On Jul 17, 2009, at 9:04 PM, Ron wrote:
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?
Yes, that's correct. In the last few tests I did, the second instance
wasn't yet aware of the new mail at the time I opened it in the first.
The 4. step seems a bit strange to me. I'd think 3. would have been
enough to cause it. Since 3. is where it reads/writes cache file. In
4. step is also reads it, but.. strange if it just worked in 3 but was
broken in 4..
Anyway, I just dist-upgraded my debian unstable yesterday and tried
with its mutt and couldn't reproduce this.
mail_location: mbox:~/Mail:INBOX=~/Mail/inbox
mbox_write_locks: fcntl dotlock
mail_plugins: antispam
Can you try if you can reproduce it without antispam?
sieve_global_path: /etc/dovecot/sieve/default.sieve
And also what if you have Sieve disabled with deliver? Or if you let
Postfix write the mail instead of using deliver?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
