On Friday, 21 January 2000 at 11:26, David T-G wrote:
> Hi, folks --
>
> I'm using 0.95.7i with some patches while I wait for a bug resolution in
> 1.0 and/or 1.0.1 (working with Sec) and I use imap to connect to a
> mailbox to prune the spam out before my wife POPs down the contents.
> I've checked with my SA and confirmed that the imapd has not changed, so
> I have the famous "I didn't do anything and now it's broken" problem :-)
>
> I have previously connected, deleted anything that was spam, synced with
> '$', and exited with 'x' and had all of the 'N' flag remain. Even if I
> check a message and find that it isn't spam, I have been able to reset
> the New flag and then sync and exit.
>
> Today I went in to check and saw "Closing mailbox" when I exited. I
> popped back in and everything, even that which I had not read, was marked
> as read. I marked each as new, synced, and exited again. I checked
> again and they were cleared. I eventually had to ftp the mailbox down,
> open it with mutt the old fashioned way, fix the flags, and then ftp it
> back up.
>
>
> Any idea what could have changed? Should I try again with a debugging
> flag on?
Hi, sorry to respond so late (I've been travelling a lot this
semester). I doubt mutt is doing it, but this is easy to verify if you
have debugging enabled. Just run mutt -d4 to get the IMAP command log
in .muttdebug0. You will be able to tell whether mutt is storing flags
for messages it shouldn't touch, destroying the new flag as a
side-effect, and possibly even whether the server is taking its own
actions. Or, you could send me the log and I could tell you (IMAP is a
somewhat obfuscated protocol), but remember to xxx out your
password.
Can you reproduce this with a more current mutt? Flag handling (and
sync) is different in the 1.1 series...
-Brendan
PGP signature
