After upgrade the SpamAssassin Server version to 3.3.1, my mail scanning stop working partially.
Below is the test.cf file for checking whether SA working as per the given score. [r...@spd SPECS]# cd /etc/mail/spamassassin/ [r...@spd spamassassin]# cat test.cf body LOCAL_DEMONSTRATION_RULE /test123/ score LOCAL_DEMONSTRATION_RULE 5 describe LOCAL_DEMONSTRATION_RULE This is a simple test rule 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 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. It seems that SA take the score 4 to consider the mail as a SPAM and rewrite the subject with *****SPAM******* Below is the log @400000004c71e02720670564 tcpserver: status: 1/100 @400000004c71e02720b8462c tcpserver: pid 4698 from 192.168.10.70 @400000004c71e02720cb1a7c tcpserver: ok 4698 spd:192.168.30.195:25 :192.168.10.70::61253 @400000004c71e027385ebf7c CHKUSER accepted sender: from <s...@test.com:s...@test.com:> remote <SPDESAI:unknown:192.168.10.70> rcpt <> : sender accepted @400000004c71e02739b381dc CHKUSER accepted rcpt: from <s...@test.com:s...@test.com:> remote <SPDESAI:unknown:192.168.10.70> rcpt <d...@test.com> : found existing recipient @400000004c71e02739b94a54 policy_check: local s...@test.com -> local d...@test.com (AUTHENTICATED SENDER) @400000004c71e02739bf3dc4 policy_check: policy allows transmission @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
