[Imap-uw] mixcvt giving me an incinsistency message size error
Mark Crispin
MRC at CAC.Washington.EDU
Tue May 8 11:01:56 PDT 2007
On Tue, 8 May 2007, nlin wrote:
> What's the best course of action in this case? I've already lost the
> original mailbox so I cannot reconvert from the original. Should I just
> leave the mailbox along or would converting it using mixcvt (I would like the
> .mix files split nicely instead of one huge 600MB file) make that message
> unreadable?
You might as well put it through mixcvt. It won't make matters any worse.
The message will be as readable in the copy as it is in the one with the
600MB file. What's more, the annoying warning won't occur in the copy.
Since you don't have the original mailbox any more, there's no point in
worrying about it. If the user hasn't complained about that message being
truncated by the bug by now, s/he probably won't ever complain.
For the record:
The bug, which was fixed in January, only impacted godzillagrams. The
message had to be at least 64K; messages less than 64K were completely
immune to the bug.
Specifically, if (size MOD 64K) < (size / 64K), then (size MOD 64K) bytes
got truncated.
For example, with a 10MB message, a message from 10,485,761 to 10,485,919
bytes would be truncated to 10,485,760 bytes, and a message from
10,485,920 to 11,534,336 (11MB) would be immune.
It really was a rare bug.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
More information about the Imap-uw
mailing list