On Tue, 5 Sep 2006, John D. Hardin wrote:
On Tue, 5 Sep 2006, nik600 wrote:
I use 5 score to tag a spam but most of spam not detected is
recognized only by HTML_MESSAGE and reports 0 scores....

*******************
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on unixmail.xxxx
X-Spam-Level:
X-Spam-Status: No, score=0.8 required=5.0 tests=HTML_MESSAGE,INFO_TLD
   autolearn=no version=3.1.0
*******************

No network tests are apparent.

Agreed.  For me, that was the biggest piece that I was missing
when I started.  I knew the network tests existed, but I didn't
realize how much of an important part they are of the whole,
comprehensive SpamAssassin picture.  I would say if you don't
have network tests going, you're missing out on half or even
more than half of what SpamAssassin has to offer.

To the original poster in this thread:  the current network
tests break down into basically 3 categories:

(1) Checksums on all or part of messages.  These include
    razor2, pyzor, and dcc.  I personally have razor2 and dcc
    set up.  These tests all require installing additional
    software -- each database has a client to query its
    particular network database of checksums.

(2) DNS-based blacklists of mail servers.

(3) DNS-based blacklists of URIs, where the message is
    scanned for links to certain URIs, and if it contains any
    of these URIs, it matches against a blacklist entry.

You basically need to install some software for #1, then
configure SpamAssassin to talk to it.  For #2 and #3, all you
need to do is choose which ones you want to enable.  I forget
what the default set is that comes enabled with SpamAssassin,
but it might be worth looking into whether you want to add a
few more.

No SARE tests are apparent.

I get pretty good results without any SARE rules at all.
Personally, I would recommend to a new user that they
focus their efforts on getting the best performance out of
SpamAssassin without adding any third-party rules first.
Once they've done that, then SARE can be appropriate if there
is still too much spam getting through.  Otherwise, if you do
SARE too early, you could end up covering over a problem in
your basic SpamAssassin configuration.

You also might want to upgrade to 3.1.3 or 3.1.4, and make sure you're
running sa-update at least weekly.

Agreed.  Although 3.1.5 is out now too.

  - Logan

Reply via email to