Please keep replies on the list...
On 2025-05-21 at 14:16:09 UTC-0400 (Wed, 21 May 2025 18:16:09 +)
Rupert Gallagher
is rumored to have said:
>> rep.mailspike.net is not even supposed to be a nameserver. I don't see why
>> you think it should have an A record
>
> NXDOMAIN is the legitimate
On 2025-05-20 at 11:32:26 UTC-0400 (Tue, 20 May 2025 15:32:26 +)
Rupert Gallagher
is rumored to have said:
Hello,
Is rep.mailspike.net working for you?
If I query 78.153.140.99 at https://mailspike.io/ip_verify I get
127.0.0.11, however if I query using dig I get no answer at all, and
On 2025-05-20 at 14:38:40 UTC-0400 (Tue, 20 May 2025 18:38:40 +)
Rupert Gallagher
is rumored to have said:
I wonder how it works for real, since mailspike.net itself fails DNS
resolution.
Not so.
$ dig mailspike.net NS
; <<>> DiG 9.10.6 <<>> mailspike.net NS
;; g
Hi,
dig -t A 99.140.153.78.rep.mailspike.net
This results in NXDMAIN, indicating that there is no current listing for
the ip address. There is no requirement in DNS that says that
'rep.mailspike.net' should be resolvable.
The mailspike nameservers are at:
dig -t NS mailspike.net
As to why
On Tue, 20 May 2025, Rupert Gallagher wrote:
Is rep.mailspike.net working for you?
If I query 78.153.140.99 at https://mailspike.io/ip_verify I get 127.0.0.11,
however if I query using dig I get no answer at all, and the name server itself
does not exist.
dig +short -t A 99.140.153.78.rep.m
I wonder how it works for real, since mailspike.net itself fails DNS resolution.
On Tuesday, May 20th, 2025 at 6:57 PM, Reindl Harald (privat)
wrote:
>
>
> suree, but nobody is using "rep.mailspike.net" since MSPIKE is part of
> the default rules
>
> header __RCVD_IN_MSPIKE_B eval:check_rb
I assume some of you is using it.
https://cwiki.apache.org/confluence/display/spamassassin/DnsBlocklists#dnsbl-block
On Tuesday, May 20th, 2025 at 5:32 PM, Rupert Gallagher
wrote:
>
>
> Hello,
>
> Is rep.mailspike.net working for you?
>
> If I query 78.153.140.99 at https://mailspike.io
