Re: duplicates with offlineimap+dovecot

[Lars Ingebrigtsen <larsi@gnus.org>]

gallego@cri.ensmp.fr (Emilio Jes?FFFAs Gallego Arias) writes:

>> *first press of g*
>> 21:02:59 [domain] 9020 UID MOVE 4063:4064,4067,4069:4072 "folder1"
>> * OK [COPYUID 1424475231 4063:4064,4067,4069:4072 26:32] Moved UIDs.
>> * VANISHED 4062,4066,4068:4072
>> * 3 RECENT
>> 9020 OK [HIGHESTMODSEQ 5193] Move completed.
>
> I interpret this as "only 4062,4066,4068:4072" got moved.

I can't find anything in the IMAP MOVE standard that says something like
that.  And it only talks about having to be careful about streaming
other commands after MOVE as a MOVE may lead to articles being
renumbered.  And the VANISHED stuff is from unrelated QRESYNC support,
if I'm reading the QRESYNC RFC correctly.

And, as you see from the VANISHED above there, most of the stuff it says
is vanished is stoff that we're not even trying to move (4062, 4066).

So I don't know what's going on on the server...

 An example:

       C: a UID MOVE 42:69 foo
       S: * OK [COPYUID 432432 42:69 1202:1229]
       S: * 22 EXPUNGE
       S: (more expunges)
       S: a OK Done

   Note that the server may send unrelated EXPUNGE responses as well, if
   any happen to have been expunged at the same time; this is normal
   IMAP operation.

   Implementers will need to read [RFC4315] to understand what UID
   EXPUNGE does, though full implementation of [RFC4315] is not
   necessary.

   Note that moving a message to the currently selected mailbox (that
   is, where the source and target mailboxes are the same) is allowed
   when copying the message to the currently selected mailbox is
   allowed.

   The server may send EXPUNGE (or VANISHED) responses before the tagged
   response, so the client cannot safely send more commands with message
   sequence number arguments while the server is processing MOVE or UID
   MOVE.

   Both MOVE and UID MOVE can be pipelined with other commands, but care
   has to be taken.  Both commands modify sequence numbers and also
   allow unrelated EXPUNGE responses.  The renumbering of other messages
   in the source mailbox following any EXPUNGE response can be
   surprising and makes it unsafe to pipeline any command that relies on
   message sequence numbers after a MOVE or UID MOVE.  Similarly, MOVE
   cannot be pipelined with a command that might cause message
   renumbering.  See [RFC3501], Section 5.5, for more information about
   ambiguities as well as handling requirements for both clients and
   servers.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no