Hi,

I'd like to better understand what caused a problem today.. and why what I did "fixed" it.

A user reported than some messages in their INBOX would open as empty. Their client was Thunderbird 2.0.0.16 and later 2.0.0.21. Client was rebooted/restarted/updated, it made do difference. There were some messages which would open without any error, but display no message content. Other messages displayed normally.

The server is CentOS 5.3 running uw-imap 2007e from EPEL. I've built mixdfix and mixrbld myself.. actually against 2007d if that makes any difference. There were no imapd errors, apart from the "Unexpected client disconnect, while reading line" which seems to be omnipresent.

INBOX is in ~/mail/INBOX and is in mix format. "mailutil check" worked fine, as did "mailutil prune INBOX 'before 1-jan-1970'". Looping across all the "data" files was OK, mixdfix gave "no repair needed" for each file.

Looking at the files, I can see that the content of the e-mails is present for the mail that is "empty" on the client.

Running "mixrbld" gave a number of "UID ran backwards" messages. Swapping the ".mixindex" and ".mixindex-rebuild" made no difference in the client behaviour.

What "fixed" the problem, was using mailtuil to copy the mailbox as a mbx file, then using mixcvt to convert it back. After that, the client displays the full content for any messages which is selected, esp those that were problematic before.

Any ideas on what was wrong ? I still have saved copies of everything if helpful.

Cheers,
Jimmy
_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Reply via email to