> > On Wed, Nov 06, 2002 at 10:08:43PM -0600, Dallas Engelken wrote: > > > > Nov 6 11:28:15 mail qmail-scanner[25804]: Clear:SA:1(0/0): > > > > This places the header X-Spam-Status: Yes, hits=0 > > required=0 in the > > > email > > > > > > Ya, the spam sub is screwed. Here is the diff fix for 1.15 > > > > No it isn't! > > > > OK OK!! Sorry. > So it's spamassassins fault.. it doesnt really matters to us > end users. :) > > > The fault is with several version of SA out there that don't > > abide by their > > own documentation. > > > > There have been cases where spamc exits 0 - but > > hits>required, cases where > > spamc exits 1 - but required>hits, etc. > > > > Do you know if this been corrected on 2.4x versions?
There was a problem introduced in 2.40 where spamd would always return a status of False, no matter what the score was. I don't think it was fixed in 2.41, but 2.42 upwards definitely work correctly. We have recently had a problem here with spamc/spamd, which resulted in it not returning anything. I have followed through the logic in sub-spamassassin, and it seems like if spamc fails, or returns an error (i.e. you get a status of 0, score of 0 and a threshold of 0) the if statement $sa_max > $sa_score is false, and the message gets tagged as spam. This has the effect of defaulting to tag all email as spam if spamassassin fails. I tried to download the patch from Dallas, but it appears to not exist anymore, so I have attached my own one line patch. Chris Hine
sub-spamassassin.pl.patch
Description: Binary data
