From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 5D42C1F4B4;
	Thu, 17 Sep 2020 20:54:08 +0000 (UTC)
Date: Thu, 17 Sep 2020 20:54:08 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: Epoch roll-over with imap
Message-ID: <20200917205408.GA21810@dcvr>
References: <20200917121852.a2zdo4j74yaejntb@chatter.i7.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200917121852.a2zdo4j74yaejntb@chatter.i7.local>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Good morning, and congratulations on 1.6.0!

Thanks.

> I'm starting to play with the new imapd mode (currently using the imap 
> daemon on public-inbox.org), and I am curious how we can make it obvious 
> to the clients that there is a new epoch available. For example, if 
> someone configures mbsync to fetch things from 
> imaps://public-inbox.org/inbox.comp.mail.public-inbox.meta.0, how will 
> they become aware when epoch 1 becomes available?

mbsync(1) appears to have a "Create" option; though I haven't
used it much.  As for informing the user of the MUA of newer
mailboxes... I don't know :x

offlineimap creates new mailboxes by default, AFAIK.

Also, I'm avoiding the word "epoch" to avoid confusion with the
v2 git repos; so the world "slice" is used throughout the IMAP
daemon code.