[clamav-users] whitelisting sender or recipient

[Reindl Harald]

and in a really good setup your spamassassin also uses clamd to add 
scores to all the other rules, dnsbl, uribl, digest-services and so the 
uncondtional whitelisting in the milter at last stage is only for dumb 
unconditional fasle positives leading to rejects

Am 19.01.2017 um 20:54 schrieb Reindl Harald:
> Am 19.01.2017 um 20:50 schrieb Paul Kosinski:
>> What if a white-listed sender later becomes part of a botnet? However
>> trustworthy the person is, their email isn't necessarily trustworthy.
>> (The "From:" address could easily be a faked, for example.)
>
> than hopefully your filter setup does not rely only on clamd,
> whitelisting is a local decision with many pros and cons and also
> depends on the signatures included in your setup
>
> there is also a difference if you have just one or more than one clamd
> instance with different signatures and whitelistings
>
> typically clamav-milter is the last stage of filtering - it's faster
> than spamassassin but spamassasin does catch much more than clamd and so
> the whole clamd can be skipped in case of sa-milter rejects
>
>> On Thu, 19 Jan 2017 08:02:39 +0100
>> z at aian.de wrote:
>>
>>> Hey there,
>>>
>>> I bet it's an easy one for you, but I couldn't find any documentation
>>> about that.
>>> What I want to do is whitelist a specific sender or recipient from
>>> the scanns.
>>>
>>> I read about the whitelist.ign2 for whitelisting signatures, but
>>> nothing about user whitelisting.
>>>
>>> Can you help?
> _______________________________________________
> clamav-users mailing list
> clamav-users at lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml