spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bowie Bailey <>
Subject Re: Odd results when using whitelisting
Date Tue, 31 May 2016 15:17:54 GMT
On 5/30/2016 10:35 AM, Nick Howitt wrote:
> Just for a bit of closure, it looks like when you use amavisd-new with 
> SA, it is amavisd-new and not SA which is adding the X-Spam headers. 
> In /etc/amavisd/api.conf there is a parameter, $sa_tag_level_deflt, 
> defaulted to -99, below which no X-Spam headers are set. If you 
> whitelist, you start at -100. So, if the rest of the tests total to 
> less than 1, you will not get an X-Spam header. This can be confirmed 
> by playing around with this parameter and by upping the amavisd log 
> level so you can see the results of all the spam tests for each e-mail 
> even if it does not get the X-Spam headers.

Amavisd-new only uses SA to generate a score for the message.  It has 
it's own settings for tagging and rejection thresholds, writes its own 
headers, and can mark a message as spam/ham or reject it based on its 
own whitelists, blacklists, and many other settings.

The bottom line is this: If you have a problem with the actual score 
being generated, look at SA.  If you have a problem with the header 
markup or with messages being rejected or let through without scanning, 
look at Amavisd.


View raw message