From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Can spam-split be used with "normal" mail splitting?
Date: Thu, 10 Apr 2003 11:17:51 -0400 [thread overview]
Message-ID: <4n8yuimleo.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <vz8yuiv1k5.fsf@viteno.dyns.net> (Norbert Koch's message of "Thu, 10 Apr 2003 17:01:46 +0200")
On Thu, 10 Apr 2003, nk@viteno.net wrote:
> I still don't use fancy-mail-splitting, but the standard way. It's
> possible to use functions with that, too, so I've added a stanza
> like
>
> (setq nnmail-split-methods
> `(("tomb" spam-split)
> ... other settings ...))
>
> but I wonder whether this DTRT. Does anyone have information about
> this?
I don't use nnmail-split-methods, and I don't know of anyone that
does with spam.el (except you :)
As long as nnmail-split-methods processing understand that nil means
"pass-through" and a string is a group name, there should be no issues
at all.
Thanks
Ted
next prev parent reply other threads:[~2003-04-10 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 15:01 Norbert Koch
2003-04-10 15:17 ` Ted Zlatanov [this message]
2003-04-11 18:06 ` Norbert Koch
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=4n8yuimleo.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).