On 2025-05-02 at 07:41:46 UTC-0400 (Fri, 02 May 2025 11:41:46 +0000)
Michael Grant via users <mgr...@grant.org>
is rumored to have said:
From "Bill Cole" <sausers-20150...@billmail.scconsult.com>
Did you do that in the "global" config at
/etc/mail/spamassassin/local.cf (or something like it with 'etc'
somewhere) or in root's user config in
/root/.spamassassin/{userprefs,local.cf,whatever} ? If it was the
latter, you need to move it to the global config.
I put it in root's user config, let me try in local.cf.
Couple things I don't understand... 1) why is this only complaining
about root
I do not know, but the way SA responds to DNSBL blocking is to stop
queries to that DNSBL for a while, so it could appear to be limited to a
single user.
and 2) if I put this in the global config
(/etc/spamassassin/local.cf), won't I be disabling the checking of
this BL for everyone?
If your resolver is blocked, it is blocked everyone.
I feel like there's some other problem here. Why am I blacklisted
from querying this BL?
That issue has been discussed extensively on this mailing list recently.
The simple answer is that Validity has reduced the limit on how many
queries can be done from unknown parties. If your queries go over their
limit, they start blocking.
These tests seem to be part of the base packages in
/usr/share/spamassassin/20_dnsbl_tests.cf. Should I really be
disabling this test globally?
If you don't want to sign up for a Validity account, then yes.
Were it not for the fact that the Validity rules have been a part of the
default rules channel for a long time, they would be disabled by default
or it would be left to users whether to have any rules for them at all.
Unfortunately, making that change now would break meta-rules that users
may have created using the Validity rules.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo@toad.social and many *@billmail.scconsult.com
addresses)
Not Currently Available For Hire
