From: Stephen Zander <gibreel@pobox.com>
Cc: ding@gnus.org
Subject: Re: Splitting, crossposts, duplicates, the universe, and everything.
Date: 20 Nov 1998 09:02:02 -0800 [thread overview]
Message-ID: <87k90qwb5h.fsf@wsfs05.mckesson.com> (raw)
In-Reply-To: Lloyd Zusman's message of "17 Nov 1998 21:27:14 -0500"
>>>>> "Lloyd" == Lloyd Zusman <ljz@asfast.com> writes:
Lloyd> (1) Do not cause all of the email that goes to the various
Lloyd> addresses to end up in the same mail spool file; rather,
Lloyd> allow each piece of email to reside in the mail spool file
Lloyd> corresponding to the user to which it is sent. For
Lloyd> example, in the case of my sample `To:' line ...
procmail, mailagent or (I think) deliver will do this for you.
Lloyd> (2) Cause Gnus to somehow (???) get its `nnml' email from
Lloyd> each of these four spool files, each one feeding a
Lloyd> different `nnml' mailbox. I would also want to perform a
Lloyd> separate splitting procedure on each of these four spool
Lloyd> files, to do the higher-granularity splitting that will be
Lloyd> necessary.
Gnus will easily do this for you. The following in my ~/.gnus.el
(setq nnml-directory "~/nnml/"
nnmail-use-procmail t
nnmail-spool-file 'procmail
nnmail-procmail-directory "~/.incoming/")
makes things Just Work.
For the record, I don't do *any* splitting within Gnus. It all
happens beforehand.
--
Stephen
---
Perl is really designed more for the guys that will hack Perl at least
20 minutes a day for the rest of their career. TCL/Python is more a
"20 minutes a week", and VB is probably in that "20 minutes a month"
group. :) -- Randal Schwartz
next prev parent reply other threads:[~1998-11-20 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 16:14 Lloyd Zusman
1998-11-17 19:09 ` Michael Welsh Duggan
1998-11-17 23:19 ` Lloyd Zusman
1998-11-17 23:23 ` Alexandre Oliva
1998-11-18 2:27 ` Lloyd Zusman
1998-11-20 17:02 ` Stephen Zander [this message]
1998-11-17 23:40 ` Karl Kleinpaste
1998-11-17 23:35 ` Alexandre Oliva
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=87k90qwb5h.fsf@wsfs05.mckesson.com \
--to=gibreel@pobox.com \
--cc=ding@gnus.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).