And btw, usually on the DNS infos of Senderscores, you can see about 3
days of lag compared to their online interface, dunno if expected on
their side, or they're facing perf issues, but that service is not a
top priority at all at least
On Mon, Apr 19, 2021 at 7:29 PM Simon Bressier <bressie...@gmail.com> wrote:
Hi Simon,
For info for few days now, the Senderscore DNS server is failing to
answer. I've pinged one relation I have at Validity so they can dig on
it.
Senderscore via DNS is a legacy service they just maintain but dunno
for how long... They are more on a mood to stop that service in the
future to push to their API usage, and you ofc need to be client to
use it :)
Seems like a good candidate to be dropped from tests.
That dnsbl is called in 20_dnsbl_tests.cf as follows:
# Validity RPBL (née Return Path Reputation Network Blacklist - RNBL):
# https://www.senderscore.org/blocklistlookup/
# (replaces RCVD_IN_RP_RNBL)
header RCVD_IN_VALIDITY_RPBL
eval:check_rbl('rnbl-lastexternal','bl.score.senderscore.com.')
describe RCVD_IN_VALIDITY_RPBL Relay in Validity RPBL,
https://senderscore.org/blocklistlookup/
tflags RCVD_IN_VALIDITY_RPBL net publish
reuse RCVD_IN_VALIDITY_RPBL RCVD_IN_RP_RNBL
...is the correct way to disable it:
local.cf: score RCVD_IN_VALIDITY_RPBL 0
?
Simon
--
Simon Wilson
M: 0400 12 11 16
