From: Scott Blachowicz <scott@statsci.com>
Cc: ding@ifi.uio.no
Subject: Re: Gnus5, procmail, and reading mail lists.
Date: Wed, 15 Nov 1995 10:46:41 -0800 [thread overview]
Message-ID: <199511151846.KAA22886@block.statsci.com> (raw)
In-Reply-To: Your message of "15 Nov 1995 01:58:44 -0500." <umt7n12fjob.fsf@honsu.cis.ohio-state.edu>
Sudish Joseph <joseph@cis.ohio-state.edu> wrote:
> If you're using mailagent as your filter, you might consider extending
> mailagent itself to generate your .overview entry. I played around
> with mailagent recently, and this seems like a simple thing to do --
> most of the hard work is already done by mailagent.
Yeah...I've already got stuff like this:
Return-path: /ding-request@ifi\.uio\.no/i {
ASSIGN list gnu/emacs/ding;
SAVE +%#list;
REJECT -t ListUpdate;
};
# Update some external files & such
<ListUpdate> {
PERL /homes/scott/var/mailagent/ListUpdate %#list;
};
which all runs in the same perl process. My plan was to update my
ListUpdate perl script to update NOV files too (right now it just makes
sure that the list is in my ~/Mail/.folders file), but I haven't gotten
around to setting things up to read the mailing lists from ding yet.
BTW, the perl process that does this doesn't happen at sendmail-delivery
time. With mailagent, my .forward file runs a "filter" program that
basically just drops the message into a queue directory that gets
processed by a different program (i.e. "mailagent") that gets kicked off
by "filter" every so often. That way the MTA is waiting for "me" to
decide what to do with each & every message.
Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc.
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
next prev parent reply other threads:[~1995-11-15 18:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-14 1:43 Steven L. Baur
1995-11-14 13:04 ` Per Abrahamsen
1995-11-15 2:42 ` Steven L. Baur
1995-11-14 16:27 ` Joe Hildebrand
1995-11-14 17:22 ` Scott Blachowicz
1995-11-14 21:35 ` Joe Hildebrand
1995-11-15 6:58 ` Sudish Joseph
1995-11-15 18:46 ` Scott Blachowicz [this message]
1995-11-15 4:37 ` Sudish Joseph
1995-11-15 14:32 ` Per Abrahamsen
1995-11-15 15:50 ` Kai Grossjohann
1995-11-15 16:13 ` Per Abrahamsen
1995-11-15 17:50 ` Steven L. Baur
1995-11-17 21:18 ` Jason L Tibbitts III
1995-11-17 21:40 ` Joe Hildebrand
-- strict thread matches above, loose matches on Subject: below --
1995-11-14 1:55 Steven L. Baur
1995-11-13 22:21 Steven L. Baur
1995-11-13 20:33 Steven L. Baur
1995-11-13 22:43 ` Joe Hildebrand
1995-11-14 19:52 ` Edward J. Sabol
1995-11-13 17:48 Mark Borges
1995-11-13 20:16 ` Joe Hildebrand
1995-11-14 0:24 ` Mark Borges
1995-11-15 6:19 ` Mark Borges
1995-11-15 8:17 ` Steven L. Baur
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=199511151846.KAA22886@block.statsci.com \
--to=scott@statsci.com \
--cc=ding@ifi.uio.no \
/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).