Re: How to read mutt-users-digest

2001-03-05 Thread kevin . christen
I left out one crucial constraint: I'm reading the mutt-users digest via IMAP, so it never gets locally delivered by procmail. I wrote a little perl script that runs formail while "preserving" some of the headers in the digest (like "sender"). But that's an ugly solution and I thought someone mi

Re: How to read mutt-users-digest

2001-03-01 Thread Christian R Molls
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [010301 21:44]: > I have a question about your formail suggestion. The individual > messages that make up the digest only have 2 headers: "From" and > "Subject". So when I run formail, the resulting messages don't have > anything unique that procmail can

Re: How to read mutt-users-digest

2001-03-01 Thread kevin . christen
I have a question about your formail suggestion. The individual messages that make up the digest only have 2 headers: "From" and "Subject". So when I run formail, the resulting messages don't have anything unique that procmail can use to identify them as being from mutt-users. Other list's dige

Re: How to read mutt-users-digest

2001-02-28 Thread Christian R Molls
* Duke Normandin <[EMAIL PROTECTED]> [010228 22:19]: > I'm currently subscribed to various mailing lists that include the > messages as "attachments" -- so it's trivial to reply to an single > message/thread. However, the mutt-users-digest "includes" all the > messages into one message. How do yo