Erik Bloodaxe wrote:
> I have a default install of Redhat 5.2. I have mail scanner using it
> and it appears to be creating a large number of false positives. The
> version of SpamAssassin is version 3.2.4 which is running on Perl
> version 5.8.8. I am using the latest version of mail scanner. I
> beleive the problem lies with spamassasin. I have a test message which
> is genuine. Running this through spamassasin with -t (test) mode as
> described below gives the output below:
>
> Running : spamassassin -t /tmp/rose2 gives at the bottom the following
> (edited for privacy) report.
>
> Spam detection software, running on the system "somehost.gold.ac.uk", 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: Hi .....content deleted for privacy.....
>
> Content analysis details: (0.0 points, 5.0 required)
>
> pts rule name description
> ---- ----------------------
> --------------------------------------------------
> 0.0 MISSING_MID Missing Message-Id: header
> 0.0 MISSING_DATE Missing Date: header
>
> So it seems (and I admit i am no expert here) that despite the low score
> spamassasin is tagging the message as spam (the subject line gets a
> {spam?} appended to on the output.
>
> Can anyone help resolve this. The RH box is upto date with all the
> spamassasin RPMs.
This is expected behavior. Read The Fine Manual... :)
-t, --test-mode
Test mode. Pipe message through and add extra report. Note
that the report text assumes that the message is spam, since in
normal use it is only visible in this case. Pay attention to
the score instead.
--
Bowie
