[Dovecot] mbox to maildir migration question and problems, dovecot-1.0.7-7.el5
Hi,
I am trying to assist a customer with a mbox to maildir migration. I have them using the latest and greatest mb2md.pl; the one that support -K, -U|-u. They have seen overwhelming success with this; however, a recent mbox introduced a new scenario and the result was that all messages were replayed in the client UI.
The mbox in question had _no_ X-UID tags. To work-a-round the issue the customer performed the following steps.
[snip] We found that the fix was to clear /var/indexes/$USER for the account and log in and log back out. After doing this X-UID's were populated for each respective message. [/snip]
The customer also noted that after the migration all messages went to ~/MailDir/new.
I would appreciate any thoughts on why this scenario played out the way it did? Is it expected that these messages should reside in ~/MailDir/new?
[config] protocol pop3 { pop3_uidl_format = %08Xv%08Xu pop3_reuse_xuidl = yes } [/config]
Thank you!
-- Eric L. Sammons, RHCE
On Wed, 2009-08-26 at 09:21 -0400, Eric Sammons wrote:
Hi,
I am trying to assist a customer with a mbox to maildir migration. I have them using the latest and greatest mb2md.pl; the one that support -K, -U|-u. They have seen overwhelming success with this; however, a recent mbox introduced a new scenario and the result was that all messages were replayed in the client UI.
The mbox in question had _no_ X-UID tags. To work-a-round the issue the customer performed the following steps.
If there were no X-UID headers, it means the mailbox had never been opened.
The customer also noted that after the migration all messages went to ~/MailDir/new.
I would appreciate any thoughts on why this scenario played out the way it did? Is it expected that these messages should reside in ~/MailDir/new?
It's just fine for messages to be in new/ directory. It basically means they have \Recent flag set, i.e. client hasn't seen them yet.
participants (2)
-
Eric Sammons
-
Timo Sirainen