30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
MBOX-Line: From tss at iki.fi Fri Nov 16 11:21:30 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Timo Sirainen <tss@iki.fi>
|
|
Date: Fri Jun 8 12:34:40 2018
|
|
Subject: [Imap-protocol] FETCH/STORE on out-of-range sequence number
|
|
In-Reply-To: <alpine.OSX.0.99999.0711161051240.7038@pangtzu.panda.com>
|
|
References: <2123708120.202451195235056495.JavaMail.root@dogfood.zimbra.com>
|
|
<6199.1195236170.977095@invsysm1>
|
|
<alpine.OSX.0.99999.0711161051240.7038@pangtzu.panda.com>
|
|
Message-ID: <1195240890.6039.172.camel@hurina>
|
|
|
|
On Fri, 2007-11-16 at 10:59 -0800, Mark Crispin wrote:
|
|
> I have NEVER seen any client confusion due to 4.1.4. For YEARS, that was
|
|
> the primary behavior in my server; and it remains the standard behavior
|
|
> for some older formats. A client MUST handle 4.1.4, because 4.1.4 is
|
|
> indistinguishable from a timing race where an external process turned off
|
|
> the \Deleted flag.
|
|
|
|
Even if clients can handle it, humans probably can't. I often have my
|
|
INBOX opened from two clients, and it would be really annoying if I had
|
|
to shut down the other one of them just to get messages expunged.
|
|
|
|
-------------- 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/20071116/965b04d6/attachment.sig>
|