From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: nnml vs nnimap fancy splitting
Date: Sun, 21 Dec 2003 18:49:55 +0100 [thread overview]
Message-ID: <87d6ai3vss.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <m2he0sz6l0.fsf@copernicus.rlent.pnet>
Maybe it is sufficient to check for the number of "*" characters in
this other X-Spam header that spamassassin creates? That would be
easy to do, even though it's not quite as intelligent.
Then there is spam.el which can check against various kinds of spam
headers. Not sure whether spamassassin is amongst the supported
programs. I think you can tell spam.el about a threshold, as well.
Kai
parent reply other threads:[~2003-12-21 17:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m2he0sz6l0.fsf@copernicus.rlent.pnet>]
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=87d6ai3vss.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).