spamassassin updated on sanpietro

[Noel Cragg]

If you're not yet using spamassassin, I'd recommend you give it a try.

Fitz said the following in July 2003:

  I've been using it for about 6 months now, and it catches 99% of my
  spam. I get about 2 false positives a month, but those are my American
  Airlines notice mails--I need to put an exception in for them.

(It's gotten much better since then.)

Karl says, "It works like a charm; don't know how I got along without
it."  I agree wholeheartedly.

----------------------------------------------------------------------

Here's again is the single, easy, quick start instruction:

  Create ~/.procmailrc and put the following rule into it:

    :0fw
    | /var/spamd/bin/spamc

That's it!  spamassassin will add "X-Spam-Status" and "X-Spam-Level"
headers to your incoming mail, which you can use to filter out spam with
procmail or any other nifty processing features your mailer might have.

Those who don't want to do either of those things may wish to put
"rewrite_subject 1" into their ~/.spamassassin/user_prefs file so that
spam messages are clearly marked as "*****SPAM***** foo bar baz."

Read the contents of /var/spamd/README for full instructions.  (Karl, I
fixed the mistakes you pointed out.)

----------------------------------------------------------------------

This latest version is 2.55 and has both razor2 and dcc support (both
are distributed checksum databases for spam).  The bayesian filtering
routines are disabled by default, because folks on the net at large
haven't yet come to consensus whether it works out of the box or not.
I'll be evaluating it for the next several months and will report back.
(If you want to try it out yourself, put "use_bayes 1" in your
~/.spamassassin/user_prefs file.)

FYI all, the spam checking daemon was down for about 20 minutes while I
performed the upgrade.  Apologies for the spam that got through to your
mailboxes.