I am running spamassassin_3.3.2-5 on debian Wheezy on a small business
server (x86).  I am getting numerous complaints about mail being falely
categorised as spam/ham.  I also use version 3.3.2 on my home server using
gentoo (amd64) and don't have these problems.  I have removed all
customisations and have reinstalled spamassassin on my debian machine.
There still seem to be problems - here's an example using the provided
sample files.  Can anybody help?

This message seems to get blocked in a lot of blocklists (which also seem
to happen to my users' messages).

Options for SA are:

# ps ax |grep spam
22408 ?        Ss     0:02 /usr/sbin/spamd --create-prefs --max-children 5
--helper-home-dir -d --pidfile=/var/run/spamd.pid

/etc/procmailrc includes this:

* < 256000
| /usr/bin/spamc
$ spamc < sample-nonspam.txt

Received: from localhost by debian.myserver.net.au
 with SpamAssassin (version 3.3.2);
 Sat, 22 Jun 2013 12:06:12 +1000
From: Keith Dawson <daw...@world.std.com>
To: t...@world.std.com
Subject: TBTF ping for 2001-04-20: Reviving
Date: Fri, 20 Apr 2001 16:59:58 -0400
Message-Id: <v0421010eb70653b14e06@[208.192.102.193]>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
 debian.myserver.net.au
X-Spam-Flag: YES
X-Spam-Level: ********
X-Spam-Status: Yes, score=8.5 required=5.0 tests=RP_MATCHES_RCVD,SAGREY,
 URIBL_AB_SURBL,URIBL_BLOCKED,URIBL_GREY,URIBL_MW_SURBL,URIBL_PH_SURBL,
 URIBL_RED,URIBL_WS_SURBL autolearn=no version=3.3.2
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_51C50694.B9FC2455"
This is a multi-part message in MIME format.
------------=_51C50694.B9FC2455
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Spam detection software, running on the system "debian.myserver.net.au", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.
Content preview:  -----BEGIN PGP SIGNED MESSAGE----- TBTF ping for
2001-04-20:
   Reviving T a s t y B i t s f r o m t h e T e c h n o l o g y F r o n t
[...]

Content analysis details:   (8.5 points, 5.0 required)
 pts rule name              description
---- ----------------------
--------------------------------------------------
-1.5 RP_MATCHES_RCVD        Envelope sender domain matches handover relay
domain
 0.0 URIBL_RED              Contains an URL listed in the URIBL redlist
                            [URIs: tbtf.com]
 0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was
blocked.
                            See

http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [URIs: tbtf.com]
 1.1 URIBL_GREY             Contains an URL listed in the URIBL greylist
                            [URIs: tbtf.com]
 0.0 URIBL_PH_SURBL         Contains an URL listed in the PH SURBL blocklist
                            [URIs: tbtf.com]
 4.5 URIBL_AB_SURBL         Contains an URL listed in the AB SURBL blocklist
                            [URIs: tbtf.com]
 1.7 URIBL_WS_SURBL         Contains an URL listed in the WS SURBL blocklist
                            [URIs: tbtf.com]
 1.7 URIBL_MW_SURBL         Contains a Malware Domain or IP listed in the
MW SURBL
                             blocklist
                            [URIs: tbtf.com]
 1.0 SAGREY                 Adds 1.0 to spam from first-time senders

------------=_51C50694.B9FC2455
Content-Type: message/rfc822; x-spam-type=original
Content-Description: original message before SpamAssassin
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Return-Path: <tbtf-appro...@world.std.com>
Delivered-To: f...@foo.com
Received: from europe.std.com (europe.std.com [199.172.62.20])
 by mail.netnoteinc.com (Postfix) with ESMTP id 392E1114061
 for <f...@foo.com>; Fri, 20 Apr 2001 21:34:46 +0000 (Eire)
Received: (from daemon@localhost)
 by europe.std.com (8.9.3/8.9.3) id RAA09630
 for tbtf-outgoing; Fri, 20 Apr 2001 17:31:18 -0400 (EDT)
Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134])
 by europe.std.com (8.9.3/8.9.3) with ESMTP id RAA08749
 for <t...@facteur.std.com>; Fri, 20 Apr 2001 17:24:31 -0400 (EDT)
Received: from world.std.com (world-f.std.com [199.172.62.5])
 by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id RAA8278330
 for <t...@facteur.std.com>; Fri, 20 Apr 2001 17:24:31 -0400 (EDT)
Received: (from dawson@localhost)
 by world.std.com (8.9.3/8.9.3) id RAA26781
 for t...@world.std.com; Fri, 20 Apr 2001 17:24:31 -0400 (EDT)
Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134])
 by europe.std.com (8.9.3/8.9.3) with ESMTP id RAA07541
 for <t...@facteur.std.com>; Fri, 20 Apr 2001 17:12:06 -0400 (EDT)
Received: from world.std.com (world-f.std.com [199.172.62.5])
 by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id RAA8416421
 for <t...@facteur.std.com>; Fri, 20 Apr 2001 17:12:06 -0400 (EDT)
Received: from [208.192.102.193] (ppp0c199.std.com [208.192.102.199])
 by world.std.com (8.9.3/8.9.3) with ESMTP id RAA14226
 for <t...@world.std.com>; Fri, 20 Apr 2001 17:12:04 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <v0421010eb70653b14e06@[208.192.102.193]>
Date: Fri, 20 Apr 2001 16:59:58 -0400
To: t...@world.std.com
From: Keith Dawson <daw...@world.std.com>
Subject: TBTF ping for 2001-04-20: Reviving
Content-Type: text/plain; charset="us-ascii"
Sender: tbtf-appro...@world.std.com
Precedence: list
Reply-To: tbtf-appro...@europe.std.com
-----BEGIN PGP SIGNED MESSAGE-----
TBTF ping for 2001-04-20: Reviving
    T a s t y   B i t s   f r o m   t h e   T e c h n o l o g y   F r o n t
    Timely news of the bellwethers in computer and communications
    technology that will affect electronic commerce -- since 1994
    Your Host: Keith Dawson
    ISSN: 1524-9948
    This issue: < http://tbtf.com/archive/2001-04-20.html >
    To comment on this issue, please use this forum at Quick Topic:
    < http://www.quicktopic.com/tbtf/H/kQGJR2TXL6H >
    ________________________________________________________________________
Q u o t e   O f   T h e   M o m e n t
    Even organizations that promise "privacy for their customers" rarely
    if ever promise "continued privacy for their former customers..."
    Once you cancel your account with any business, their promises of
    keeping the information about their customers private no longer
    apply... you're not a customer any longer.
    This is in the large category of business behaviors that individuals
    would consider immoral and deceptive -- and businesses know are not
    illegal.
    -- "_ankh," writing on the XNStalk mailing list
    ________________________________________________________________________
..TBTF's long hiatus is drawing to a close
    Hail subscribers to the TBTF mailing list. Some 2,000 [1] of you
    have signed up since the last issue [2] was mailed on 2000-07-20.
    This brief note is the first of several I will send to this list to
    excise the dead addresses prior to resuming regular publication.
    While you time the contractions of the newsletter's rebirth, I in-
    vite you to read the TBTF Log [3] and sign up for its separate free
    subscription. Send "subscribe" (no quotes) with any subject to
    tbtf-log-requ...@tbtf.com . I mail out collected Log items on Sun-
    days.
    If you need to stay more immediately on top of breaking stories,
    pick up the TBTF Log's syndication file [4] or read an aggregator
    that does. Examples are Slashdot's Cheesy Portal [5], Userland [6],
    and Sitescooper [7]. If your news obsession runs even deeper and you
    own an SMS-capable cell phone or PDA, sign up on TBTF's WebWire-
    lessNow portal [8]. A free call will bring you the latest TBTF Log
    headline, Jargon Scout [9] find, or Siliconium [10].
    Two new columnists have bloomed on TBTF since last summer: Ted By-
    field's roving_reporter [11] and Gary Stock's UnBlinking [12]. Late-
    ly Byfield has been writing in unmatched depth about ICANN, but the
    roving_reporter nym's roots are in commentary at the intersection of
    technology and culture. Stock's UnBlinking latches onto topical sub-
    jects and pursues them to the ends of the Net. These writers' voices
    are compelling and utterly distinctive.
    [1]  http://tbtf.com/growth.html
    [2]  http://tbtf.com/archive/2000-07-20.html
    [3]  http://tbtf.com/blog/
    [4]  http://tbtf.com/tbtf.rdf
    [5]  http://www.slashdot.org/cheesyportal.shtml
    [6]  http://my.userland.com/
    [7]  http://www.sitescooper.org/
    [8]  http://tbtf.com/pull-wwn/
    [9]  http://tbtf.com/jargon-scout.html
    [10] http://tbtf.com/siliconia.html
    [11] http://tbtf.com/roving_reporter/
    [12] http://tbtf.com/unblinking/
    ________________________________________________________________________
S o u r c e s
> For a complete list of TBTF's email and Web sources, see
    http://tbtf.com/sources.html .
    ________________________________________________________________________
B e n e f a c t o r s
    TBTF is free. If you get value from this publication, please visit
    the TBTF Benefactors page < http://tbtf.com/the-benefactors.html >
    and consider contributing to its upkeep.
    ________________________________________________________________________
    TBTF home and archive at http://tbtf.com/ . To unsubscribe send
    the message "unsubscribe" to tbtf-requ...@tbtf.com. TBTF is Copy-
    right 1994-2000 by Keith Dawson, <daw...@world.std.com>. Commercial
    use prohibited. For non-commercial purposes please forward, post,
    and link as you see fit.
    _______________________________________________
    Keith Dawson               daw...@world.std.com
    Layer of ash separates morning and evening milk.
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.2 for non-commercial use <http://www.pgp.com>
iQCVAwUBOuCi3WAMawgf2iXRAQHeAQQA3YSePSQ0XzdHZUVskFDkTfpE9XS4fHQs
WaT6a8qLZK9PdNcoz3zggM/Jnjdx6CJqNzxPEtxk9B2DoGll/C/60HWNPN+VujDu
Xav65S0P+Px4knaQcCIeCamQJ7uGcsw+CqMpNbxWYaTYmjAfkbKH1EuLC2VRwdmD
wQmwrDp70v8=
=8hLB
-----END PGP SIGNATURE-----

------------=_51C50694.B9FC2455--

Reply via email to