nmh-workers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [nmh-workers] Email VERY slow (about 20 hour delay) leaving google m


From: Kevin Cosgrove
Subject: Re: [nmh-workers] Email VERY slow (about 20 hour delay) leaving google mail server(s)
Date: Sat, 25 Aug 2018 12:14:18 -0700

On 25 August 2018 at 9:29, Ralph Corderoy <address@hidden> wrote:

> Hi Kevin,
> 
> > What trouble is the nmh-workers list seeing with regard to my email
> > address?
> 
> As an example, Mailman saw a bounce in trying to send your subscription
> a copy of your email to the list.  :-)
> 
>     This is a Mailman mailing list bounce action notice:
> 
>         List:       nmh-workers
>         Member:     address@hidden
>         Action:     Subscription bounce score incremented.
>         Reason:     Excessive or fatal bounces.
> 
>     The triggering bounce notice is attached below.
> 
>     X-Failed-Recipients: address@hidden
> 
>       address@hidden
>         all relevant MX records point to non-existent hosts
> 
> I think there's inconsistent DNS at play.  nmh's Mailman is consistently
> seeing the bad data.  Google flip-flops and so you get your mail, but
> sometimes after a delay.
> 
>     $ whois cosgroves.us | grep 'Name Server'
>     Name Server: ns1.scnresearch.com
>     Name Server: ns2.scnresearch.com
>     $
>     $ dig +short +identify @ns1.scnresearch.com cosgroves.us mx
>     10 qiclab.scnresearch.com. from server 205.238.26.97 in 159 ms.
>     $ dig +short +identify @ns2.scnresearch.com cosgroves.us mx
>     10 qiclab.scn.rain.com. from server 216.128.96.24 in 149 ms.
>     $
> 
> `qiclab.scnresearch.com' != `qiclab.scn.rain.com'.
> 
>     $ dig +short +identify @ns1.scnresearch.com cosgroves.us ns
>     NS2.SCNRESEARCH.COM. from server 205.238.26.97 in 156 ms.
>     NS1.SCNRESEARCH.COM. from server 205.238.26.97 in 156 ms.
>     $ dig +short +identify @ns2.scnresearch.com cosgroves.us ns
>     QICLAB.SCN.RAIN.COM. from server 216.128.96.24 in 148 ms.
>     NS2.SCNRESEARCH.COM. from server 216.128.96.24 in 148 ms.
>     $
> 
> ns2 introduces a new NS into the mix.
> 
> There might be other inconsistencies too.
> 
> Hopefully, you'll get this email as I'm also sending it direct.
> Or if not, you'll think to check the web archive.  :-)

The root cause of the problem was that rain.com got sold without notice,
and seemingly against an agreement, and the new owner immediately
changed DNS records. There's a lot of history on the ownership and
running of rain.com that goes back to 1990, and at least 100 entities
were effected.

A friend of mine was a co-founder of RAINet, which contained rain.com.
He spent a lot of time during the last weeks recovering from that 
change. I don't want to imagine what it takes to update 30 years of 
domain growth expecting to find rain.com as it was. Ouch!

My friend's system(s) are my upstream MX. He fixed all of them, but 
missed *.us domains. That's fixed now.


Ralph, he said your info was VERY helpful, and that all of those tests
should look fine now.

THANKS SO MUCH!


--
Kevin





reply via email to

[Prev in Thread] Current Thread [Next in Thread]