Bill Cole wrote:
On 23 Dec 2020, at 13:57, Grant Taylor wrote:
On 12/22/20 11:03 PM, Bill Cole wrote:
Do you have a setup that supports per-user preferences? e.g.: real
system accounts.
Sort of. The recipient is a real Unix account. However I don't think
my milter is configured to use per recipient filtering.
You definitely would know if it were.
If so, you can disable off individual rules for a user by giving them
a score of 0 in ~/.spamassassin/user_prefs if they have a real
account or in whatever you use for per-user prefs if they are virtual
users.
Would that truly disable the tests? Or does SpamAssassin still run
the tests but ignore the result?
I have not tested it, but I'm pretty sure that it actually disables the
tests, as it does with any other type of rule.
Only if you set the score to 0 on the rule that actually triggers the
DNSBL call. Until recently(ish) this was the only way to selectively
disable DNSBLs enabled by default in the stock rules.
skip_rbl_checks or dns_available should work per-user by way of
userprefs. dns_query_restriction has now been around for a few releases
and makes it easier to be sure you've disabled all DNS lookups for a
particular domain.
-kgd
