Re: How to read mutt-users-digest
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 might have a better one. On Fri, Mar 02, 2001 at 02:12:34AM +0100, Christian R Molls wrote: > * [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 use to identify them as being from > > mutt-users. Other list's digests typically do one of two things: > > > > * Include other headers in the individual messages, such as "To" or > > "Cc", or > > > > * Prepend something to the subject, like "[wm-users] Original subject > > here". > > > > How do you handle this when using formail to split the mutt-users > > digest? > The trick is to run formail from your .procmailrc. I'll post the > example from the procmailex manpage: > :0: > * ^Subject:.*surfing.*Digest > | formail +1 -ds >>surfing > All messages containing "surfing" and "Digest" in the Subject: header > (that condition should match the surfing list digests) are piped > to formail which splits them, skipping what it considers the first > message. The output, ie the separate messages, are appended to folder > "surfing". So all the messages from one digest go into one mailbox. No > more filtering is necessary. > For mutt-users you would use something like: > :0: > * ^Subject:.*mutt-users-digest > | formail +1 -ds >>mutt-users > chris > - -- > christian r. mollsthe rain descended, > [EMAIL PROTECTED] and the floods came > >
Re: How to read mutt-users-digest
* [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 use to identify them as being from > mutt-users. Other list's digests typically do one of two things: > > * Include other headers in the individual messages, such as "To" or > "Cc", or > > * Prepend something to the subject, like "[wm-users] Original subject > here". > > How do you handle this when using formail to split the mutt-users > digest? The trick is to run formail from your .procmailrc. I'll post the example from the procmailex manpage: :0: * ^Subject:.*surfing.*Digest | formail +1 -ds >>surfing All messages containing "surfing" and "Digest" in the Subject: header (that condition should match the surfing list digests) are piped to formail which splits them, skipping what it considers the first message. The output, ie the separate messages, are appended to folder "surfing". So all the messages from one digest go into one mailbox. No more filtering is necessary. For mutt-users you would use something like: :0: * ^Subject:.*mutt-users-digest | formail +1 -ds >>mutt-users chris -- christian r. mollsthe rain descended, [EMAIL PROTECTED] and the floods came
Re: How to read mutt-users-digest
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 digests typically do one of two things: * Include other headers in the individual messages, such as "To" or "Cc", or * Prepend something to the subject, like "[wm-users] Original subject here". How do you handle this when using formail to split the mutt-users digest? Kevin On Wed, Feb 28, 2001 at 11:55:34PM +0100, Christian R Molls wrote: snip > The mutt-users list is available both digested and as separate mails. > You might want to unsubscribe from the the digest and make a new > subscription for regular mails. Check out www.mutt.org for advice. > However, if you want to keep receiving the digest, you could still > split it locally. "formail", which is part of the "procmail" package, > can split incoming digests. > Check out the procmailex manpage, in case procmail is already > installed on your system, otherwise get it from www.procmail.org. > - -- > christian r. mollsthe rain descended, > [EMAIL PROTECTED] and the floods came > >
Re: How to read mutt-users-digest
* 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 you guys get around this? It's a real > PITA, IMHO. I've contacted the maintainer of the digest at gbnet.net, but > have yet to receive a reply. I'm new to using Mutt, so there may be an > easy, "local" solution to this. Tia... The mutt-users list is available both digested and as separate mails. You might want to unsubscribe from the the digest and make a new subscription for regular mails. Check out www.mutt.org for advice. However, if you want to keep receiving the digest, you could still split it locally. "formail", which is part of the "procmail" package, can split incoming digests. Check out the procmailex manpage, in case procmail is already installed on your system, otherwise get it from www.procmail.org. -- christian r. mollsthe rain descended, [EMAIL PROTECTED] and the floods came
How to read mutt-users-digest
Hi... 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 you guys get around this? It's a real PITA, IMHO. I've contacted the maintainer of the digest at gbnet.net, but have yet to receive a reply. I'm new to using Mutt, so there may be an easy, "local" solution to this. Tia... -- -duke Calgary, Alberta, Canada
