I have further read the Migration documentation and someone pointed out to me two good questions:
1 - If I use the modified mb2md.pl -U the program creates a dovecot-uidlist. Or if I can produce this list is there a way I can make dovecot use this list when it creates the dovecot-index file sets the first time it accesses the mailbox? Aka is there a command line option using dovecot or doveadm that creates the indexes based on the dovecot-uidlist that I can script for each mailbox I transfer? 2 - How/where/when do I use "pop3_reuse_xuidl=yes" in the dovecot.conf file for the first time each mailbox is read? Does this option need to be used after the first time (it is not set by default in my new server config). ________________________________ From: Tim E. <silent_wum...@yahoo.com> To: Dovecot List Mailing <dovecot@dovecot.org> Sent: Friday, September 7, 2012 3:32 PM Subject: [Dovecot] Dovecot 1.x POP3 to Dovecot 2.x POP3 mbox to Maildir best transfer program/method I have a box running Dovecot 1.x POP3 only server using mbox format. I want to port the mail over to a Centos 6.3 box running a Dovecot 2.x POP3 only server using Maildir format. The main thing I want to do is support XUID/read/unread status so the transfer is transparent for the end user. I have been able to achieve transfers from the mbox format to Maildir but loose the XUID/read/unread status so that the Thunderbird client always re-downloads all the mail as if it were new. Ive googled and I have tried the following: dsync : dovecot 1.x server is too old and doesnt support the command? mb2md.pl: transfers the mbox to maildir and creates file dovecot-uidlist but the Thunderbird client redownloads the files virtualmin copy-mailbox: transfers the mailbox to Maildir but doesnt reproduce the dovecot indexes. Any thoughts would be appreciated. I would like to produce a howto of the process when I am done.
