well one thing to think about.
Since there are already servers and clients deployed, unless we allow
there to be some way to distinguish between a MOVE extension that sends
EXPUNGES and one (legacy) that doesn't, do we need to call this MOVE2?
Adrien
----
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
WinGate 7 is released! - http://www.wingate.com/getlatest/
------ Original Message ------
From: "Timo Sirainen" <[email protected]>
To: "Jan Kundrát" <[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: 31/05/2012 9:52:07 p.m.
Subject: Re: [imap5] Should unsolicited EXPUNGE responses be returned
during UID MOVE?
On Thu, 2012-05-31 at 11:41 +0200, Jan Kundrát wrote:
- Sending the untagged EXPUNGE/VANISHED and only after them the COPYUID
might be troublesome for some clients -- for example, my code will react
to EXPUNGE by removing the cached data for that message from the on-disk
cache. When the COPYUID arrives, the data is already gone. (My code
actually ignores COPYUID for now anyway, but that's not relevant here.)
- Postponing of the untagged EXPUNGE/VANISHED until after the tagged OK
is probably a bad idea, so what about a special "VANISHED (MOVED)" which
would hint the client that the data shall not be purged immediately?
Another possibility:
C: a UID MOVE 42:45 forble
S: * OK [COPYUID 432432 1202:1205] Messages moved
S: * 15 EXPUNGE
S: * 15 EXPUNGE
S: * 15 EXPUNGE
S: * 15 EXPUNGE
S: a OK Done
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
