On 1/9/2023 3:55 AM, Matus UHLAR - fantomas wrote:
Until I can get around to updating I'm considering just nuking the
actual tests from the ruleset.
Much easier and reliable way:
dns_query_restriction deny spamhaus.org
Charles Sprickman skrev den 2023-01-09 08:04:
Trying this on half the pair, I assume this hits all subdomains of
spamhaus.org?
Never ran into that parameter in my searches for this.
On 09.01.23 09:26, Benny Pedersen wrote:
never read perldoc Mail::SpamAssassin::Conf ?
some people don't repeatedly read it thorough.
Henrik forgot this is pr domain, so fully domain including subdomain
seen in "rndc querylog" in bind logs !
spamassassin -D -t spamtestmsg 2>&1 | less
dns_query_restriction deny dwl.dnswl.org list.dnswl.org
dns_query_restriction deny multi.uribl.com
imho score foo 0 is a bug
no, it's documented feature - rules with score 0 are not run.
However, joe a aka the OP should be more interested in finding out why
are his DNS queries going through an open resolver and fixing the real
issue.
Right you are. It now appears resolved (cough, cough . . .).
Spamhaus site provided this quick test: "dig 2.0.0.127.zen.spamhaus.org
+short" which with variant "dig @my.local.dns.serv
2.0.0.127.zen.spamhaus.org +short", allowed me to pretty quickly sort it
out.
A lot of cobwebs needed to be cleared out, but, seems to be working as
advertised.
Thanks to all for their patience and suggestions.
joe a.
