wasm-demo/demo/ermis-f/imap-protocol/cur/1600095112.22911.mbox:2,S

31 lines
1.4 KiB
Plaintext

MBOX-Line: From tss at iki.fi Sun Jun 10 08:31:34 2007
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun 8 12:34:39 2018
Subject: [Imap-protocol] Concurrent Mailbox Changes.
In-Reply-To: <Pine.BSO.4.64.0706071648360.5267@vanye.mho.net>
References: <46581509.7050201@buni.org> <1180182602.32181.1919.camel@hurina>
<alpine.OSX.0.99.0705260804430.3501@pangtzu.panda.com>
<1181230565.6639.15.camel@mike-laptop>
<alpine.OSX.0.99.0706070855180.11475@pangtzu.panda.com>
<Pine.BSO.4.64.0706071648360.5267@vanye.mho.net>
Message-ID: <1181489494.5181.1.camel@hurina>
On Thu, 2007-06-07 at 17:02 -0600, Philip Guenther wrote:
> The RECENT response clearly needs to be sent whenever the number messages
> with the \recent flag has changed. It's probably technically legal to
> suppress it when that count hasn't changed (say, if new messages have
> arrived that aren't \recent or if an equal number of \recent messages have
> been expunged as have arrived), but it may not be wise for a server to do
> that.
Dovecot has been doing that for years. Haven't heard any complains yet.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20070610/c420e59b/attachment.sig>