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.
Nick
On 26/05/2016 07:17, Nick Howitt wrote:
On 26/05/2016 00:29, Reindl Harald wrote:
Am 25.05.2016 um 21:58 schrieb Nick Howitt:
and what is the problem run a local unbound on port 1053 and just add
"dns_server [127.0.0.1]:1053" to your SA-configuration when one thinks
he is capable to run his own servers?
I've tried looking and failed. Any chance of pointing me to where this
is documented?
seriously?
unbound.conf:
interface: 127.0.0.1
port: 1053
/etc/mail/spamassassin/local.cf:
dns_server [127.0.0.1]:1053
https://www.google.com/search?q=unbound.conf
https://www.google.com/search?q=spamassassin+dns_server
Seriously, yes. I'd found and set up unbound OK, if you'd read another
of my posts. I had not found it for SA. Not good searching, but I had
not - and I'd tried a few of the links on google and the some man pages.
OK, I've been heavily shot at for my set up which is totally
irrelevant to the question I posed and not a pleasant experience. Is
there any possibility of some help with the problem I posted about?
