Re: spamassassin4.x problem

Benny Pedersen skrev den 2025-02-14 00:05:
> Bill Cole skrev den 2025-02-13 21:29:
>> On 2025-02-13 at 11:13:43 UTC-0500 (Thu, 13 Feb 2025 17:13:43 +0100)
>> natan <[email protected]>

>>> Feb 13 17:02:06 amavis5 amavis[9316]: (09316-01) _WARN: check: 
>>> dns_block_rule RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating 
>>> /var/amavis/var/.spamassassin/dnsblock_bl.score.senderscore.com (This 
>>> means DNSBL blocked you due to too many queries. Set all affected 
>>> rules score to 0, or use "dns_query_restriction deny 
>>> bl.score.senderscore.com" to disable queries)
>>> 
>>> 
>>> dig +short 
>>> 127.0.0.1.bzdaby.clicks.mlsend.com.dnsblock_bl.score.senderscore.com 
>>> @127.0.0.1
>>> dig 
>>> 127.0.0.1.bzdaby.clicks.mlsend.com.dnsblock_bl.score.senderscore.com 
>>> @127.0.0.1
>> 
>> Try that *WITHOUT* '@127.0.0.1', which tells dig to use 127.0.0.1 
>> exclusively, rather than to use the system configuration defined in  
>> resolv.conf says. Unless you've told SA to use some other resolver, it 
>> uses whatever the system is configured for.
> 
> agre @... should not be used for testing

in my home:

xpoint@tux ~ $ dig 
127.0.0.1.bzdaby.clicks.mlsend.com.dnsblock_bl.score.senderscore.com

; <<>> DiG 9.18.29 <<>> 
127.0.0.1.bzdaby.clicks.mlsend.com.dnsblock_bl.score.senderscore.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14722
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: ca6e8baad3cde3210100000067ae7ea9c7da761318c96980 (good)
;; QUESTION SECTION:
;127.0.0.1.bzdaby.clicks.mlsend.com.dnsblock_bl.score.senderscore.com. 
IN A

;; AUTHORITY SECTION:
score.senderscore.com.	10800	IN	SOA	s0.rpdns.net. 
dnsadmin.senderscore.com. 2025021313 2700 3600 604800 86400

;; Query time: 203 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri Feb 14 00:22:17 CET 2025
;; MSG SIZE  rcvd: 203

note SERVER: :=)