Re: Bypass scanning based on recipient

[Damian]

Also, I don't think @spam_lovers_maps and @bypass_spam_checks_maps
will work because it relies on the recipient being the only address to
receive the email. If there are other recipients, the regular
processing occurs.

That is not true depending on how you mean it. This is what it looks 
like when a single spamlover & bypasser receives a GTUBE spam mail:

(00275-04) Passed CLEAN {RelayedInbound}, [172.21.0.1] 
<u...@example.net> -> <spamlo...@example.com>, Message-ID: 
<20210422140259.121...@example.com>, mail_id: HmLW8bEk7kgq, Hits: -, 
size: 320, queued_as: 250 2.0.0 Ok, 39 ms
Here we have multiple envelope recipients:

(00276-04) Passed SPAM {DiscardedInbound,RelayedInbound,Quarantined}, 
[172.21.0.1] <u...@example.net> -> <spamlo...@example.com>, 
quarantine: /var/lib/amavis/virusmails, Message-ID: 
<20210422140259.121...@example.com>, mail_id: gB4RBtc0NaED, Hits: 
1000.998, size: 337, queued_as: 250 2.0.0 Ok, 118 ms
(00276-04) Blocked SPAM {DiscardedInbound,RelayedInbound,Quarantined}, 
[172.21.0.1] <u...@example.net> -> <u...@example.com>, quarantine: 
/var/lib/amavis/virusmails, Message-ID: 
<20210422140259.121...@example.com>, mail_id: gB4RBtc0NaED, Hits: 
1000.998, size: 337, 118 ms

So yes, the mail has been processed by SpamAssassin, but forwarded to 
spamlover nonetheless.