Re: Odd results when using whitelisting

[Reindl Harald]

Am 24.05.2016 um 18:49 schrieb Nick Howitt:

Hi,
I'm using SpamAssassin v3.3.1-3 on ClearOS 6.7 (a CentOS derivative) and
I believe it is invoked by amavis-new. I have a whitelist line in local.cf:

    whitelist_from *@avivaemail.co.uk @m.avivaemail.co.uk *@tomtom.com
    *@dpd.co.uk *@clearos.com *@peacocks-mail.com

most of them has SPF, others maybe DKIM or both



just use "whitelist_auth" instead

so don't use "whitelist_from" which opens the door for forging senders and completly bypass your filter for no good reason

In e-mail headers from clearos.com I get the following:

dunno about your issue, maybe amavisd is part of it
URIBL_BLOCKED - you really really should fix that



http://uribl.com/refused.shtml

*never* use a forwarind/ISP nameserver for a inbound MX

it harms your results masive since you mostly get nor responses from DNSBL, DNSL and also builtin DNSWL which are in palce to reduce false positives

This looks OK with the X-Spam entries.

From peacocks-mail.com I get:

In this case there are no X-Spam entries, as if whitelisting completely
bypasses spamassassin but both go through amavisd-new. Can you help me
understand what is happening?

signature.asc
Description: OpenPGP digital signature