You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Erik Bloodaxe <E....@gold.ac.uk> on 2009/08/19 17:23:43 UTC
Assistence needed with spamassasin under RedHat 5.2
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.
Thanks
Erik
Re: Assistence needed with spamassasin under RedHat 5.2
Posted by Anthony Peacock <a....@chime.ucl.ac.uk>.
Hi,
Erik Bloodaxe wrote:
> Bowie Bailey wrote:
>> 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.
>>
>>
> Ok,
>
> Thanks and sorry for not spotting this. However, how can I investigate
> this problem further. The problem either lies with spam assasin,
> mailscanner or the interaction between them.
> I can reproduce the problem by sending the message through the system?
> Which spamassasin options should I use (I have treid -d but this make
> not a lot of sence to me).
Your email hints that you are running MailScanner. I think this may be
a MailScanner config issue.
Do you have RBLs switched on in MailScanner?
Check the "Spam List =" and "Spam Lists To Be Spam =" config settings.
MailScanner will mark a message as spam if the number of RBLs configured
in "Spam Lists To Be Spam =" are hit, regardless of the SpamAssassin score.
--
Anthony Peacock
CHIME, UCL Medical School
WWW: http://www.chime.ucl.ac.uk/~rmhiajp/
Study Health Informatics - Modular Postgraduate Degree
http://www.chime.ucl.ac.uk/study-health-informatics/
Re: Assistence needed with spamassasin under RedHat 5.2
Posted by Erik Bloodaxe <E....@gold.ac.uk>.
Bowie Bailey wrote:
> 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.
>
>
Ok,
Thanks and sorry for not spotting this. However, how can I investigate
this problem further. The problem either lies with spam assasin,
mailscanner or the interaction between them.
I can reproduce the problem by sending the message through the system?
Which spamassasin options should I use (I have treid -d but this make
not a lot of sence to me).
Rob
Re: Assistence needed with spamassasin under RedHat 5.2
Posted by Bowie Bailey <Bo...@BUC.com>.
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
Re: Assistence needed with spamassasin under RedHat 5.2
Posted by MySQL Student <my...@gmail.com>.
Hi,
> 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.
Try adding some debugging output, and first look for something obviously wrong:
# spamassassin -D -t /tmp/rose2 2>&1 | less
Go line-by-line looking for something that stands out as obviously wrong.
Consider obfuscating your message, replacing your domain with
"example.com", for instance, and uploading it to pastebin.com. Then
post a link here so we can all view the message for further ideas.
Regards,
Alex