On Sat, Mar 16, 2013 at 12:14 -0400, Ryan Kavanagh wrote: > On Fri, Mar 08, 2013 at 11:40:09AM +0000, Wolodja Wentland wrote: > > It seems to me as if this but manifested itself directly after the latest > > dovecot upload (1:2.1.7-7) to sid, but I am not entirely sure if this is > > indeed the source. I have, however, not experienced this problem before and > > if > > Mark and Ryan run dovecot 1:2.1.7-7 locally as well I would be almost > > convinced that this is related.
> I tried downgrading to > ii dovecot-common 1:2.1.7-6 all Transitional package for > dovecot > ii dovecot-core 1:2.1.7-6 amd64 secure mail server that > supports > ii dovecot-imapd 1:2.1.7-6 amd64 secure IMAP server that > supports > from snapshot.debian.org[0] with which I don't recall having any issues, > but the issue still occurs. I have just downgraded dovecot-{core,imapd} to 1:2.1.7-6 and have *as of now* not yet experienced any problems. I will keep on using this setup for longer and will fervently continue moving mails between folders. The symptoms I ran into before the downgrade were, as noted earlier, different from those that Ryan experienced in that mutt did not crash for me but "merely" ran into two errors, namely: * tls_socket_read (A TLS fatal alert has been received.) * imap_sync_message: STORE failed The latter is being raised in imap.c [0] in the imap_sync_message function. I have to admit that this function looks a bit, well, hacky, but I am even more convinced that this is a problem with mutt's IMAP handling or a change in dovecot's implementation (or both). [0] http://codesearch.debian.net/show?file=mutt_1.5.21-6.2%2Fimap%2Fimap.c&line=1112&numfiles=3#L1112 -- Wolodja <deb...@babilen5.org> 4096R/CAF14EFC 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
signature.asc
Description: Digital signature