From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 762F51F4B4 for ; Thu, 17 Sep 2020 12:18:57 +0000 (UTC) Received: by mail-qk1-x72f.google.com with SMTP id w186so1950654qkd.1 for ; Thu, 17 Sep 2020 05:18:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition; bh=uc0xhYy41AIwmoL07oxkV4xIC7zSJGbZAmb0XMTwLwU=; b=CUQvnXi9tzSKZ1nch14UkTy3a6MjZV78luzHQCAViMUWSTgHz2yVYGqRV/0XZFYNeO NNztO6Pd+ZlxUqCayt6ZhUhQ2swD3mUEdDRCA5Z1wSwO/LZGwMuzX1DwAo6kKaZ/Qpgk QlkrSk9qvDhdObaojYgL2OeMfa0PxmaZrPv44= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition; bh=uc0xhYy41AIwmoL07oxkV4xIC7zSJGbZAmb0XMTwLwU=; b=R8O62SEW3xUys+ldkkfIICuKAQ+asNvIsLmzbO1x4KZvUBJajEz2QsTjeVIDVzYPhd kBUBv2qpRUN3/1af9ItheTG2/plkI8t4yev5bKP+2F1tmwYkfv2wdcI71CjcVBvLVqbf J+BEwv4PDx+ax5IDk9lD+GjSh6FDAr04475i6FOmMCKEL9ZUrsJocbxicsMH0ZZB2ui8 21fiskqnwLrrjN1rQiF2NC9/utS/EELYLNfHdHL6sTh109Gbkl1YCREEz5QmVtNwFpLa wfDCiaeY6Bps1//j2R/R6SFBwC/3b1RQ2dWeQ1qjoM6tFwXsPDaEo1qkmPUa0rtaWQLA xtug== X-Gm-Message-State: AOAM532Aib/xaX7RBGaUPwHDELiM0v6GYk6eiZLo3uHX/Vat/sk9aMOu rIrC7s48Gc+Q5LH5XW8K/jC57V/zDsCWn32f X-Google-Smtp-Source: ABdhPJzAUZ75GhkvkmzLEcxEbPvsM0vLdcxk+7F/nm5VCkCG8/0CQE4QWPwlWDr/AkeRf82a5xCVjw== X-Received: by 2002:a37:6805:: with SMTP id d5mr26768404qkc.116.1600345135656; Thu, 17 Sep 2020 05:18:55 -0700 (PDT) Received: from chatter.i7.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id n1sm1461201qte.91.2020.09.17.05.18.54 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 17 Sep 2020 05:18:55 -0700 (PDT) Date: Thu, 17 Sep 2020 08:18:52 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Epoch roll-over with imap Message-ID: <20200917121852.a2zdo4j74yaejntb@chatter.i7.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Good morning, and congratulations on 1.6.0! 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? Best regards, -K