From: tebennett@mindspring.COM (Tony E. Bennett)
Subject: Re: New Digest Handling?
Date: 20 Apr 1999 23:09:43 -0400 [thread overview]
Message-ID: <m3wvz6fz48.fsf@oh-no.mindspring.com> (raw)
In-Reply-To: Jack Vinson's message of "20 Apr 1999 09:29:04 -0500"
Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:
>
> Actually, I usually jump into the group, mark all the articles and move
> them to another group so that I can read all the digests together as
> regular mail. I don't suppose anyone has come up with mail-processing code
> that bursts digests and dumps them into a group completely behind the
> scenes? (I've written a script that I fire on the digest message. I'd
> really like something that works as mail is retrieved.)
'formail' does this fairly well. I run it from procmail on certain lists.
# burst out the digest
:0:
* ^Subject:.*Digest.*pilot
| formail +1 -ds >> palmpilot
--
--tbennett t.bennett@computer.org
next prev parent reply other threads:[~1999-04-21 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 7:40 E. David Bell
1999-04-20 14:29 ` Jack Vinson
1999-04-21 3:09 ` Tony E. Bennett [this message]
1999-06-12 2:16 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wvz6fz48.fsf@oh-no.mindspring.com \
--to=tebennett@mindspring.com \
--cc=t.bennett@computer.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).