Hello everyone,
I don't know if this is a bug in Mutt or in Binc but it certainly hurts when it
happens.
In mutt, if you change a flag on an email and a new message arrives in the currently
selected folder before the status flags are synced with the server, mutt effectively
is wrecked. There are numerous 'parse errors' that are reported in the status line
and the general solution is to quit out of mutt, at which point it segfaults, and/or I
must kill it from another terminal.
I notice this several times a day on mailing lists which are hosted in nearby servers
where I may reply to a message and have my copy delivered locally before mutt has a
chance to save the 'replied' flag to the server. When it does, the whole connection
goes down in flames. I keep meaning to report it but I always forget to cut/paste the
failure messages about the parse error. I finally decided that I'd at least mention
it to ask if anyone else has noticed a similar problem when syncing status flags to
the server.
Normally I'd just assume it was Mutt, given that this doesn't occur with several other
IMAP clients in the same interaction modes, but I know that with certain other flavors
of IMAP server, Mutt is perfectly capable of synchronizing changed flags after
delivery of new email to the mailbox.
My first thought was concurrency and lack of proper mail store locks, but Mutt
(version 1.4) only uses a single connection to the server for all its work. This is
against binc 1.0.25, with SSL turned on. I can't recall for sure off the top of my
head if this was also occurring in earlier versions of Binc.
C=)
--
--------------------------------------------------------------------------
Better the hard truth than the comforting fantasy. -- Carl Sagan
--------------------------------------------------------------------------
Caskey <caskey*technocage.com> /// TechnoCage Inc.
--------------------------------------------------------------------------
A presumption on your part does not constitute an obligation on my part.
