From: Jonas Steverud <d4jonas@dtek.chalmers.se>
Subject: Re: spam-splitter.el
Date: Sat, 20 Jul 2002 10:15:53 +0200 [thread overview]
Message-ID: <wtny9c6ak7a.fsf@licia.dtek.chalmers.se> (raw)
In-Reply-To: <m3ptxjs15a.fsf@thneed.na.wrq.com>
Michael Slass <mikesl@wrq.com> writes:
> Here's something I've been using to search the *body* of incoming
> mails for spam-like phrases. It started with the tip on how to do so
> from the Gnus manual, and kinda grew from there.
Regarding nnmail-split-search-spam-body-trace, is it possible to get
it to insert a little header line in each mail?
I.e. it adds "X-NNMail-Split-Spam-Trace: Foo". I use procmail for my
spamkilling and formail is handy to insert a header for which rule
matched and use that to do some statistics on which rules catches the
most spam.
It is IMHO a nice feature that could be added. If I made myself clear.
/Jonas, who won't use it since he has a very nice .procmailrc and
hence doesn't use splitting at all.
--
( www.dtek.chalmers.se/~d4jonas/ ! Wei Wu Wei )
( Meaning of U2 Lyrics, Roleplaying ! To Do Without Do )
prev parent reply other threads:[~2002-07-20 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 0:18 spam-splitter.el Michael Slass
2002-07-20 8:15 ` Jonas Steverud [this message]
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=wtny9c6ak7a.fsf@licia.dtek.chalmers.se \
--to=d4jonas@dtek.chalmers.se \
/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).