[Dovecot] critical X-UID reordering problem after upgrade from 1.1 to 1.2

Rob Henderson robh at cs.indiana.edu
Sat Aug 22 05:36:34 EEST 2009


Timo Sirainen wrote:
>
> One easy solution would be to change UIDVALIDITY (the large number in 
> X-IMAP: or X-IMAPbase: header) of each mailbox. Then the client will 
> redownload all mails.

I just tried that on one of the inboxes and it seemed to do the trick!  
I just inc'ed the number that was there by 1 but does it really matter 
how I change it as long as it changes?  I'm just thinking about how to 
script this for all the inboxes so can I just change them all to the 
same number for the sake of expediency or do they need to be unique, or 
higher than the number there now, or ???

>
> I can't really think of why UIDs would have changed though. I think 
> v1.1's and v1.2's mbox handling code is pretty much the same.

I haven't had much time to study exactly how all the inboxes were 
changed but I did diff a couple from right before and right after the 
upgrade and there were *lots* of diffs in just the X-UID values.  At a 
quick look, it sure seemed like a reordering had been done to remove the 
holes in the numbering in some kind of compaction-like operation.

Thanks!!!

  --Rob


More information about the dovecot mailing list