[Imap-protocol] MOVE is a pipeline

[Timo Sirainen]

On 15.6.2010, at 6.34, Mark Crispin wrote:


> However, as in COPY, the only way that untagged EXPUNGE in MOVE can work

> is as I stipulated; having effect AFTER the execution of a MOVE and not

> impacting the sequence as processed by MOVE.  Since MOVE does its own

> expunging, this in turn means that any untagged EXPUNGE has to refer to

> the MSN state after the expunges by MOVE.


That would require client to wait for the tagged reply to MOVE to find out if it succeeded or not, before it can process any untagged replies. I don't think any other command works that way. Maybe instead:

a MOVE 1:100 elsewhere
* MOVED
* 3 EXPUNGE
a OK

vs.

a MOVE 1:100 elsewhere
* 2 EXPUNGE
a NO Some of the messages were expunged.

Other random things I thought of:
 - Trying to MOVE an expunged message that's still accessible in session should fail the MOVE instead of create a copy of it?..
 - Should describe QRESYNC interaction with HIGHESTMODSEQ updates (and maybe VANISHED)