Re: mutt/2183: Messages marked as old even though mark_old set to no
The following reply was made to PR mutt/2183; it has been noted by GNATS.
From: David Ball <db-mutt@xxxxxxxx>
To:
Cc: bug-any@xxxxxxxxxxxxx
Subject: Re: mutt/2183: Messages marked as old even though mark_old set to no
Date: Sun, 12 Feb 2006 19:10:51 +0000
On Sun, Feb 12, 2006, Derek Martin wrote:
> > >Description:
> > I get my mail using fetchmail, which passes it to exim to deliver
> > locally (via procmail).
>
> It's hard to say if this would affect the problem you're writing
> about, but you could just have fetchmail send the mail to procmail
> directly:
>
> mda "/usr/bin/procmail -f -"
>
> That should be a bit more efficient. And I suppose it's possible that
> it might even fix your problem... It might be the MDA that's
> mistakenly marking the mail as old.
Sadly this makes no difference.
Looking into this more, it appears to be the POP3 server at the other
end which is inserting "Status: O" headers into the mail. If I add
'dropstatus' to the fetchmail config, then all the messages are marked
as new (including, of course, ones that I have read on the server, so
this doesn't actually solve the problem).
I'm contacting the server admin to see if there has been a change to the
config/upgrade of the POP3 server. Alternatively it may be a change in
behaviour in mutt to honour 'Status: O' even if mark_old is set to no -
do you know if there has been such a change?
Either way, it doesn't look like mutt is at fault. :) Although, it
might be nice to have a config option to always ignore 'Status: O'...
Thanks,
David
--
David Ball <db-mutt@xxxxxxxx>