Spamassassin not detecting spam

[George]

Hi,

Thanks for your replies. Here's what I get when running that command:
[root at cpm-group Mail-SpamAssassin-3.2.4]# spamassassin -t < ./sample-spam.txt
Subroutine FuzzyOcr::O_CREAT redefined at
/usr/lib/perl5/5.8.8/Exporter.pm line 65.
 at /usr/lib/perl5/5.8.8/i386-linux-thread-multi/POSIX.pm line 19
Subroutine FuzzyOcr::O_EXCL redefined at
/usr/lib/perl5/5.8.8/Exporter.pm line 65.
 at /usr/lib/perl5/5.8.8/i386-linux-thread-multi/POSIX.pm line 19
Subroutine FuzzyOcr::O_RDWR redefined at
/usr/lib/perl5/5.8.8/Exporter.pm line 65.
 at /usr/lib/perl5/5.8.8/i386-linux-thread-multi/POSIX.pm line 19
X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on cpm-group.com
Subject: Test spam mail (GTUBE)
Message-ID: <GTUBE1.1010101 at example.net>
Date: Wed, 23 Jul 2003 23:30:00 +0200
From: Sender <sender at example.net>
To: Recipient <recipient at example.net>
Precedence: junk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This is the GTUBE, the
        Generic
        Test for
        Unsolicited
        Bulk
        Email

If your spam filter supports it, the GTUBE provides a test by which you
can verify that the filter is installed correctly and is detecting incoming
spam. You can send yourself a test mail containing the following string of
characters (in upper case and with no white spaces and line breaks):

XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X

You should send this test mail from an account outside of your network.

(no report template found)

Also when I run: sendmail email at domain.com < ./sample-spam.txt it gets
fine to my email marked as non spam
X-CPMGroup-MailScanner: Found to be clean
X-CPMGroup-MailScanner-From: root at cpm-group.com
X-Spam-Status: No

Please help.

Thanks


>  spamassassin -t < sample-spam.txt
>  will take the sample-spam.txt (shipped as part of the SpamAssassin
> distribution) and process it through your SpamAssassin setup and print a
> report on the end of it that shows what rules it hits and what its score is.
> Do that, and see what it says; do come back and tell us what it says.
>
>  If it says 0 then you've got a SpamAssassin problem and really need to ask
> on the SpamAssassin list.
>
>  If it gets 1000 points, then SpamAssassin is basically working, and the
> problem lies elsewhere. If so, then tell us what settings in
> MailScanner.conf you changed ("MailScanner --changed" will help you there).
>
>  To start with, you don't actually need to change any settings in that file
> at all, except for the ones the "Installing MailScanner with Postfix" told
> you to. So I hope you didn't go through it randomly changing stuff :-)
>
>  Jules
>
>  --
>  Julian Field MEng CITP CEng
>  www.MailScanner.info
>  Buy the MailScanner book at www.MailScanner.info/store
>
>  MailScanner customisation, or any advanced system administration help?
>  Contact me at Jules at Jules.FM
>
>  PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>  PGP public key: http://www.jules.fm/julesfm.asc
>
>
>  --
>  This message has been scanned for viruses and
>  dangerous content by MailScanner, and is
>  believed to be clean.
>
>
>
>  --
>  MailScanner mailing list
>  mailscanner at lists.mailscanner.info
>  http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>  Before posting, read http://wiki.mailscanner.info/posting
>
>  Support MailScanner development - buy the book off the website!
>