replication is unable to fix uidvalidity difference
Ken Murchison
murch at andrew.cmu.edu
Wed Sep 12 09:58:53 EDT 2007
David Carter wrote:
> On Mon, 3 Sep 2007, Bron Gondwana wrote:
>
>> Reading the sync_client protocol, I notice that do_mailbox_single
>> doesn't actually send the uidvalidity as part of the local mailbox
>> status from the server, so it can't even tell there's a difference.
>>
>> [...], something to keep in mind next time there's a protocol change.
>
> Here's a fix, which should be orthogonal to the SHA1 UUID work (which
> requires a protocol change anyway).
>
> http://www-uxsup.csx.cam.ac.uk/~dpc22/cyrus/patches/2.3cvs/sync_uidvalidity.patch
>
>
> Also a small cleanup. do_mailbox_work() doesn't use the uniqueid argument:
>
> http://www-uxsup.csx.cam.ac.uk/~dpc22/cyrus/patches/2.3cvs/sync_do_mailbox_work.patch
Is there any reason why we want this to be a separate command, rather
than just adding UIDVALIDITY to the MAILBOXES command?
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
More information about the Cyrus-devel
mailing list