Re: A few mutt questions

[Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday, January 28 at 09:28 AM, quoth Dan H.:
>On Sat, Jan 26, 2008 at 04:05:10PM -0600, David Champion wrote:
>
>> It certainly supports this, but it depends on the mail source itself to
>> say what's read.  Mutt can alter these flags, but so can other tools.
>
>Well, long story short, I see neither 'N' or 'O' flags. My mail comes from
>three IMAP accounts via fetchmail, exim, procmail.

If memory serves, the way that MH folders keep track of new versus 
read messages is the same way that mboxes do, which is via a header 
embedded in the message (Status: or something like that). It seems 
entirely possible to me that the IMAP servers are using some similar 
means of storing messages, and that the messages may already HAVE that 
header in them (possibly indicating that they have been read) when you 
fetchmail them. Thus, when they are re-delivered to your mailbox via 
procmail, they look like messages that have been previously read. 
Since mutt doesn't keep a separate record of what has or has not been 
read in mailboxes (it relies on the mailbox's contents to be 
accurate), that could potentially be the problem.

Open up those messages with a pager (e.g. less Lists/mutt/61), and see 
if they don't have something that looks like:

     Status: read

already in them. If they do, then fixing the problem is a simple 
matter of adding a filter to your procmail script, right near the 
beginning, that looks like this:

     :0 f
     |formail -I Status

~Kyle
- -- 
Selfishness is not living as one wishes to live, it is asking others 
to live as one wishes to live.
                                                         -- Oscar Wilde
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFHne7xBkIOoMqOI14RAufeAJ9GSxBqaoBxSPuXa6cd/W/3VkNIEACeKq4l
MJ8/9n27Yn7BG9qjKOzsCzQ=
=zVqm
-----END PGP SIGNATURE-----