On Fri, Jun 01, 2012 at 08:02:31PM +0000, Adrien W. de Croy wrote: > It does clearly state EXPUNGE is required, and it even looks like > we implemented it that way.
I'm just going to double check mine as well: . fetch 1:* uid * 1 FETCH (UID 322) * 2 FETCH (UID 332) * 3 FETCH (UID 333) * 4 FETCH (UID 334) * 5 FETCH (UID 336) * 6 FETCH (UID 338) * 7 FETCH (UID 340) * 8 FETCH (UID 341) * 9 FETCH (UID 342) * 10 FETCH (UID 343) * 11 FETCH (UID 344) * 12 FETCH (UID 345) * 13 FETCH (UID 346) * 14 FETCH (UID 347) . OK Completed (0.000 sec) . xmove 1:2 inbox.sub * 1 EXPUNGE * 1 EXPUNGE . OK [COPYUID 1338587236 322,332 1:2] Completed . uid xmove 340 inbox.sub * 5 EXPUNGE . OK [COPYUID 1338587236 340 3] Completed . enable qresync * ENABLED CONDSTORE QRESYNC . OK Completed . xmove 1:* inbox.sub * VANISHED 333:334,336,338,341:347 . OK [COPYUID 1338587236 333:334,336,338,341:347 4:14] Completed Looks like it supports both with and without UID. I would argue that since MOVE implies COPY + STORE + EXPUNGE, then using the non-UID version of MOVE implies that you have to follow the pipelining rules as if you had issued that COPY, that STORE and that EXPUNGE. Which means you can't pipeline multiple non-UID moves, because the EXPUNGE command can't be pipelined with other actions until it's been completed. I'll go back and respond to that particular point in fact. Bron. _______________________________________________ imap5 mailing list [email protected] https://www.ietf.org/mailman/listinfo/imap5
