From: Jonas Steverud <tvrud@bredband.net>
Subject: Re: [Q] why using spam.el ?
Date: Wed, 21 Apr 2004 22:10:28 +0200 [thread overview]
Message-ID: <m2ad15gki3.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se> (raw)
In-Reply-To: <4n1xmhgpma.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 21 Apr 2004 14:19:57 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Wed, 21 Apr 2004, didier@lrde.epita.fr wrote:
>
>> In my own experience, I use spamassassin via procmail
[...]
> Where people find spam.el most useful is not in detecting spam, but
> in catching and training on misclassified spam and ham.
Let's not forget one of the more important ones: For us that cannot
use preprocessed mail, e.g. by Spamassasin (which is easy to use if
you can filter through procmail and then let Gnus fetch from a file),
because Gnus fetches the email from a POP server and then splits it.
I read the docs for using SA using :prescript/:postscript (or whatever
the parameters where) and I can't say it was an elegant solution.
Not all ISPs supplies spam filters for their customers...
(: spam-split) and spam.el is then very handy indeed! It also gives me
a easy mean of using several spamfilters and easily use BBDB as a
whitelist. Very nice!
--
( http://hem.bredband.net/steverud/ ! Wei Wu Wei )
( Meaning of U2 Lyrics, Roleplaying ! To Do Without Do )
next prev parent reply other threads:[~2004-04-21 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 16:39 Didier Verna
2004-04-21 18:19 ` Ted Zlatanov
2004-04-21 20:10 ` Jonas Steverud [this message]
2004-04-22 10:45 ` Didier Verna
2004-04-22 11:30 ` Exaggerated use of Face and X-Face (was: [Q] why using spam.el ?) Reiner Steib
2004-04-22 16:27 ` Exaggerated use of Face and X-Face Wes Hardaker
2004-04-22 17:50 ` Reiner Steib
2004-04-22 21:28 ` Wes Hardaker
2004-04-22 21:41 ` Steve Youngs
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=m2ad15gki3.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se \
--to=tvrud@bredband.net \
/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).