'Upgrade' from Cyrus 2.3.18 to 2.4.17 - need to rebuild '.seen' files?

[Adam Tauno Williams]

On Fri, 2013-05-31 at 10:48 +0100, Karl Pielorz wrote:
> Further to my original post...
> If I run imapd up - and access the mailbox, I see the following logged:
> "
> May 31 10:44:20 imaps[7401]: seen_db: user fred opened 
> /vol/host/imap/user/f/fred.seen
> May 31 10:44:20 imaps[7401]: Index upgrade: user.fred (10 -> 12)
> May 31 10:44:20 imaps[7401]: open: user fred opened INBOX
> "
> After this, I can run 'reconstruct user.fred' (and don't get any 
> segfault/core from reconstruct).
> So - is there anyway to run something that will go through and do this 
> 'Index upgrade' on all the .seen files? - That way I can be sure the mail 
> store is upgraded to the new version of Cyrus IMAP before I let masses of 
> people log in to the system?

(a) it will happen on-the-fly, as you see.  So I'd only really be
worried about large or very busy mailboxes.  Most mailboxes will update
on-the-fly with no issues [provided your I/O is sufficient]

(b) you can do a reconstruct on all you mailboxes; just be careful of
the options you use.  
  If you use delayed expunge then you want "-k".  
  If you are using replication then perhaps "-s".
Dump the mailbox list to a flat file and use it to run reconstruct for
every mailbox;  or with "-r" and run it for every user.

There are lots of messages about the 2.3.x -> 2.4.x upgrade back in the
archives.