spamassassin required hits adjustment.
Christopher Albert
sysadmin at DMS.UMONTREAL.CA
Tue Jun 25 22:16:28 IST 2002
Julian Field wrote:
> At 21:54 25/06/2002, you wrote:
>
>> Thanks for the "proof read" Julian.
>
>
> No worries.
>
>> I've got bigger problems. SA suddenly started rating most of my mail
>> at 255
>> (including all mail from this list). It also appears to be called twice
>> consecutively
>
>
> Eek. Never seen that one before. What SA are you running? They have
> produced a 2.31 in the past few days, which seems to be working okay for
> me. 255 hits implies the return code from SA could have been negative
> (it's
> shifted right 8 times). Test SA thoroughly with the manual "spamassassin"
> script in their distribution.
>
I had the same problem with 255 from the original message of this thread.
SA2.31, MailScanner-3.20-6 :
X-MailScanner: Found to be clean, Found to be clean
X-MailScanner-SpamCheck: SpamAssassin (255 hits)
Both of which I just installed yesterday.
This is hard to reproduce. The sample spam comes checks out correctly.
More information about the MailScanner
mailing list