From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: new spam.el functionality
Date: Thu, 23 Jan 2003 21:44:23 -0500 [thread overview]
Message-ID: <m365sf2rnc.fsf@heechee.beld.net> (raw)
In-Reply-To: <87u1fzh3zf.fsf@eris.void.at> (Andreas Fuchs's message of "Thu, 23 Jan 2003 22:52:37 +0000 (UTC)")
On Thu, 23 Jan 2003, asf@void.at wrote:
> Today, Ted Zlatanov <tzz@lifelogs.com> wrote:
>> Regular expression matching against headers. You define a list of
>> regular expressions in spam-regex-headers-spam and
>> spam-regex-headers-ham, and set spam-use-regex-headers to t.
>> spam-split will invoke spam-check-regex-headers.
>
> Hm, isn't whitelist and blacklist functionality a subset of the
> regex matching functionality? Could these three be merged easily?
I wouldn't merge them, they have very different purposes and
white/blacklists store their lists in files, but you could certainly
emulate white/blacklists with regex-headers if you wanted. I don't
think anyone would.
Ted
next prev parent reply other threads:[~2003-01-24 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 17:35 Ted Zlatanov
2003-01-23 22:52 ` Andreas Fuchs
2003-01-24 2:44 ` Ted Zlatanov [this message]
2003-01-24 3:23 ` Raja R Harinath
2003-01-24 4:33 ` Ted Zlatanov
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=m365sf2rnc.fsf@heechee.beld.net \
--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).