Lately it feels as though amavisd-new has been moving in the direction of just being a handler for AV scanning. Anyhow, there are many annoyances in the current version. Here is a copy paste from the forums for a resolution with the latest stable no longer adding spam scoring in the headers. I'm hoping this will help a few of you on the list that currently use the postfix/amavisd spam filter setup.
Original url: http://forums.gentoo.org/viewtopic-t-710521-highlight-spamassassin.html?sid=234cd91d4c7420bf94d8bb787748fd55 Posted: Wed Oct 29, 2008 11:23 am Post subject: Reply with quote <http://forums.gentoo.org/posting.php?mode=quote&p=5263655> ------------------------------------------------------------------------ I worked with the author of amavisd and found that there is NO WAY to make amavisd add X-Spam-* headers to every message and still have a [possible-spam] level with X-Spam-Status still set to NO without a modification to the code. Below is the modification I made that allows me to check mail in this fashion: *From 0 - 3.5 X-Spam* added, X-Spam-Status: NO, subject unchanged *From 3.5-5.0 X-Spam* added, X-Spam-Status: NO, subject shows [possible-spam] *From 5.0-6.0 X-Spam* added, X-Spam-Status: YES subject: **spam** (procmail moves to Spam folder) *From 6.0-8.01 X-Spam* added, X-Spam-Status: YES subject **blatant-spam** (procmail moves to Spam folder) * From 8.01+ Spam is killed. The modification: in sub add_forwarding_header_edits_per_recip (2.6.1): *Code:* --- amavisd.orig 2008-06-29 02:37:58.000000000 +0200 +++ amavisd 2008-10-27 19:58:16.000000000 +0100 @@ -11125,4 +11125,5 @@ my($bypassed) = $r->bypass_spam_checks; my($do_tag) = $r->is_in_contents_category(CC_CLEAN,1); +$do_tag = 1; my($do_tag2) = $r->is_in_contents_category(CC_SPAMMY); my($do_kill) = $r->is_in_contents_category(CC_SPAM);
