replication is unable to fix uidvalidity difference

2007-09-03 Thread Bron Gondwana
Our checkreplication script has managed to find uidvalidity differences between a couple of folders. I'm not sure how they crept in, probably other bugs causing reconstructs with missing index files or something. Anyway... Reading the sync_client protocol, I notice that do_mailbox_single

Re: replication is unable to fix uidvalidity difference

2007-09-03 Thread David Carter
On Mon, 3 Sep 2007, Bron Gondwana wrote: Our checkreplication script has managed to find uidvalidity differences between a couple of folders. I'm not sure how they crept in, probably other bugs causing reconstructs with missing index files or something. Anyway... Reading the sync_client

Re: replication is unable to fix uidvalidity difference

2007-09-03 Thread Bron Gondwana
On Mon, 3 Sep 2007 10:07:36 +0100 (BST), David Carter [EMAIL PROTECTED] said: On Mon, 3 Sep 2007, Bron Gondwana wrote: Our checkreplication script has managed to find uidvalidity differences between a couple of folders. I'm not sure how they crept in, probably other bugs causing

Re: replication is unable to fix uidvalidity difference

2007-09-03 Thread Bron Gondwana
On Mon, 3 Sep 2007 10:24:43 +0100 (BST), David Carter [EMAIL PROTECTED] said: On Mon, 3 Sep 2007, Bron Gondwana wrote: My reading was a reconstruct without cyrus.index. If you reconstruct without a header it will get a new UniqueID, but if you reconstruct without an index it doesn't