The problem with the Example mailbox is not a mailbox corruption problem;
the mailbox is fine.
The problem is a bug in the mix driver in imap-2006, and has already been
fixed in imap-2006a (which entered release status Friday evening).
The problem occurs when a message has an internaldate (received date) with
a timezone that is east of the prime meridian; that is, has a positive
time zone. Although positive time zones were recognized, the code had a
path in which a variable was uninitialized and thus hit the consistency
check which issued the message.
I learned about this problem soon after people in Europe tried imap-2006.
Unfortunately, it seems that nobody in the Eastern Hemisphere tried any of
the imap-2006 development snapshots, otherwise this problem would have
been caught prior to then.
[Obligatory beg: PLEASE try the development snapshots!!]
Deleting the .mixindex file is not an appropriate fix. There will be a
tool in the futureto regenerate the .mixindex file if corrupted. But, in
this case, nothing was corrupted. The tool would simply restore the
.mixindex with the same positive timezone internaldate that caused the
error.
To summarize: upgrade to imap-2006a and that problem will go away. mix
still has an unvarnished record of no corrupted mailboxes. That actually
surprises me, and I'm sure that record will be broken sooner or later.
But it hasn't happened yet.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw