On Fri, Jul 17, 2009 at 08:24:04PM -0400, Timo Sirainen wrote:
> 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?
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.
> Or is your mutt built with IDLE support or something?
Not sure. It's vanilla mutt from Sid as of yesterday.
> Could you also paste your dovecot -n output, maybe there's something
> that could be related to this.
# dovecot -n
# 1.2.1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.30-1-amd64 x86_64 Debian squeeze/sid
log_timestamp: %Y-%m-%d %H:%M:%S
protocols: imaps
login_dir: /var/run/dovecot/login
login_executable: /usr/lib/dovecot/imap-login
mail_max_userip_connections: 50
first_valid_uid: 1000
last_valid_uid: 1010
first_valid_gid: 1000
last_valid_gid: 1010
mail_location: mbox:~/Mail:INBOX=~/Mail/inbox
mbox_write_locks: fcntl dotlock
mail_plugins: antispam
auth default:
passdb:
driver: passwd-file
args: /etc/dovecot/%Ls.passwd
userdb:
driver: passwd
plugin:
sieve_global_path: /etc/dovecot/sieve/default.sieve
antispam_trash: trash;Trash;Deleted Items
antispam_spam: spam/surely;spam/probably
antispam_unsure: spam/maybe
antispam_mail_sendmail: /usr/bin/sudo
antispam_mail_sendmail_args: -H;-n;-u;amavis;/usr/bin/sa-learn
antispam_mail_spam: --spam
antispam_mail_notspam: --ham
antispam_mail_tmpdir: /tmp
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
