Okay, to begin with, note that the blacklist to which you're referring is user-configurable. So you can't enforce it once it's been set up.
If that's acceptable to you, then an easy alternative would be to use a filter instead of a blacklisting. Ideally you would have that entire department in a unique subdomain, and then you could create a filter like
If FROM contains (or "matches wildcard condition", or "is" if you haven't set up a subdomain) then Discard
(That's from the web interface, not sure what the CLI syntax would be.)
But if you've set up a subdomain, then why not just do your blacklist as follows? zmprov -l ma <original email id > amavisBlacklistSender <subdomain>
Because the blacklistsender can take just a domain, and then it'll block everything from that domain.
Your final option would be to hack amavisd.conf.in, using the per-recipient personal tables. This would have the virtue of NOT being user-configurable. Just add a high enough score to the blacklisted addresses, and all mail from them will be blocked without going into Junk. |