On Mon, 2010-08-23 at 08:16 +0530, Suhag Desai wrote:
> After upgrade the SpamAssassin Server version to 3.3.1, my mail
> scanning stop working partially.
> Below is the setting for local.cf
>
> rewrite_header Subject ****SPAM****
> report_safe 1
> required_score 5.0
> use_bayes 1
> bayes_auto_learn 1
>
> endif # Mail::SpamAssassin::Plugin::Shortcircuit
Is that the exact content of your local.cf? That doesn't even pass lint
testing. Did you do 'spamassassin --lint'?
> Let me explain in details. When I set the required score to 5.0, mail
> scanning is not working properly. When I send the mail with “test123”
> with required score 5, SA not consider it spam but when I set the
> required score to 4, SA consider it spam the same mail. I have check
> the same with many other test.
What do the X-Spam headers read SA generates?
You are using a test rule with a score of 5.0, which is the same as the
required_score threshold. Odds are, there are other rules firing on the
message a well.
If the sum of these other rules is less than 0, but greater than -1,
you'd get exactly what you just described.
> Below is the log
> @400000004c71e02d1471a28c simscan:[4698]:CLEAN
> (-1.00/12.00):5.3640s:test123:192.168.10.70:s...@test.com:d...@test.com
> @400000004c71e02f35bee364 tcpserver: end 4698 status 0
> @400000004c71e02f35bf0e5c tcpserver: status: 0/100
There is no SA logs in there.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
