On Sat, 2009-07-18 at 09:25 +0930, Ron wrote: > So here's what I can do to reproduce it, confirmed again after the last > imaptest run: > > 1. Start 2 instances of mutt into the same imap folder. > 2. echo "hmm" | mail -s test ron > 3. <imap-fetch-mail> in one of the mutt instances to update the index > of what is in the mailbox. > 4. Open the new message in it.
So 3 and 4 are on the same mutt instance, and the second mutt instance haven't even see the mail yet by the time the corruption happens? Or is your mutt built with IDLE support or something? I was just testing with Ubuntu's mutt and couldn't reproduce it. I could try at home with Debian unstable's mutt too if that would cause it.. Could you also paste your dovecot -n output, maybe there's something that could be related to this.
signature.asc
Description: This is a digitally signed message part