spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arne Jensen <>
Date Sun, 31 Jan 2021 15:30:21 GMT

Den 31-01-2021 kl. 15:35 skrev Matus UHLAR - fantomas:
> On 31.01.21 12:02, Georg Faerber wrote:
>> On 21-01-31 12:58:48, Axb wrote:
>>> Cisco forgot to renew
>>> 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:
> 1800  IN      A

If this one causes false positives for anyone, then that actual
person/organisation (obviously, MX operator side) that it causes false
positives for, are the one to blame.

Spamcop hasn't ever listed "" a valid return code, have they?


> The response code from the SpamCop server to indicate a queried IP is
> listed is 

If everyone had done proper return code checking, e.g. response =, and not been triggering on anything else, then everyone's
mail systems would have kept running just fine, without any issues, at all.

After all, any false positives are solely done by the lack of proper
validation of return codes on the receiving end.

Note that the domain simply hasn't been renewed! It hasn't
*YET* been "overtaken by someone", as you say.

It is *STILL* under the auto-renew period where the Spamcop admins have
the possibility to renew the domain, and restore functionality. It is
very common (more like standard, than just common) for the "Registry
Expiry Date" to show another year upon expiration and until the domain
has been renewed or deleted. You want to check the actual registrar
whois server (e.g. for the actual expiration date from
the registrar. That one still says 2021-01-30.

Med venlig hilsen / Kind regards,
Arne Jensen

View raw message