Ian Mortimer
2006-Sep-11 05:16 UTC
[Dovecot] Corrupt mbox folders after migration from uw-imap
After migrating our mail server from uw-imap to dovecot at the weekend we've had a few corrupted mbox folders. I assume this is due to messages with bad Content-length headers. Is there any way of checking the Content-length of messages in mbox folders? Thanks -- Ian
Frank Cusack
2006-Sep-11 17:37 UTC
[Dovecot] Corrupt mbox folders after migration from uw-imap
On September 11, 2006 3:16:27 PM +1000 Ian Mortimer <ian at physics.uq.edu.au> wrote:> After migrating our mail server from uw-imap to dovecot at the > weekend we've had a few corrupted mbox folders. I assume this is > due to messages with bad Content-length headers. Is there any way of > checking the Content-length of messages in mbox folders?Use formail (part of procmail) to extract the messages as individual files (mh style). Then it's trivial to either check, recompute, or just remove the Content-length headers. Make sure you only do this for the "main" message, not any Content-Length text in the body or any attachments. Then recombine each message into an mbox file. -frank
Magnus Stenman
2006-Sep-14 09:03 UTC
[Dovecot] Corrupt mbox folders after migration from uw-imap
Ian Mortimer wrote:> I managed to create the simplest possible folder that shows the problem. > It has just two messages in it. If I delete the top message the > first 6 characters (From .) get removed from the From line of the next > message leaving the folder corrupt. > > This is on RHEL4 x86_64, so before posting it to bugzilla I decided to > test it on RHEL4 i386 with the save dovecot version: > dovecot-0.99.11-4.EL4. > > This time, no corruption of the inbox when the first message is deleted. > > So I tested another problem folder and got the same result: > corruption on 64 bit, no corruption on 32 bit. > Posted as Bugzilla Bug 206376my problems have all been on i386>