Re: Bypass spam check for specific recipients in specific policy_bank

Simon Wilson <[email protected]>
Newsgroups gmane.mail.virus.amavis.user
Message-ID <20210312194251.Horde.VxYD2z642vQGR_xJlwBgxO0@mail.simonandkate.net>
----- Message from Matus UHLAR - fantomas <[email protected]> ---------
    Date: Fri, 12 Mar 2021 09:24:01 +0100
    From: Matus UHLAR - fantomas <[email protected]>
Subject: Re: Bypass spam check for specific recipients in specific policy_bank
      To: [email protected]


> On 12.03.21 17:16, Simon Wilson wrote:
>> For a specific POLICY_BANK (attached to submission port) I *do*  
>> want to scan emails sent by my users for spam content (experience  
>> of a compromised user in the past), so I do *not* have  
>> "bypass_spam_checks_maps   => [1]," set in the submission port's  
>> policy_bank.
>>
>> What is the right way to exclude email with specific RECIPIENT  
>> addresses from spam checks when processed through that same  
>> policy_bank?
>
> I have following:
>
> %bypass_spam_checks = {
>        '[email protected]'            => 1,
>        '[email protected]'       => 1
> };
>
> in global config, but I believe you could put that info policy bank config
> as well.
>
> -- 
> Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> Boost your system's speed by 500% - DEL C:\WINDOWS\*.*


----- End message from Matus UHLAR - fantomas <[email protected]> -----



Thanks Matus, following works within the policy bank per suggestion to  
list from Damian - slightly different approach to your suggestion, but  
it does the job:

$policy_bank{POLICY_BANK} = {
     # ...
     bypass_spam_checks_maps =>  [{
         '[email protected]' => 1,
         'bypass-that.tld' => 1,
         '.' => 0,
     }],
};

-- 
Simon Wilson
M: 0400 12 11 16
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.