On 31 Jan 2021, at 10:04, Matus UHLAR - fantomas wrote:

On 31.01.21 15:43, Axb wrote:
On 1/31/21 3:35 PM, Matus UHLAR - fantomas wrote:
On 31.01.21 12:02, Georg Faerber wrote:
On 21-01-31 12:58:48, Axb wrote:
Cisco forgot to renew spamcop.net
Registry Expiry Date: 2022-01-30T05:00:00Z

That's still one year to go, isn't it?

seems that this has been overtaken by someone who provides false positives
for anyhing:

;; ANSWER SECTION:
1.0.0.127.bl.spamcop.net. 1800  IN      A       91.195.240.87

It's parked & wildcarded. Sedo_typical

looks like answer 91.195.240.87 should be treated as NXDOMAIN

Only a carelessly misconfigured system will treat "any A record" as an active DNSBL listing. We are almost 2 decades past the first time a DNSBL had this problem and responsibly developed tools (like SA) avoid it by default.

In the case of SpamCop and SA, the default RCVD_IN_BL_SPAMCOP_NET rule will only match if there's a TXT record with 'spamcop' in its content. Other DNSBL rules in SA require hitting specific 127.* values in A records.

--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire

Reply via email to