[NBLUG/talk] OT - Sending mail to comcast.net

[Don Forbes]

Mark Street wrote:
> Hi,
> 
> Is anyone else having troubles sending to comcast.net customers?  My mail 
> servers have been getting timed out messages since mid to late September.
> 
> Nov 17 21:35:56 penguin postfix/smtp[11362]: connect to 
> mx2.comcast.net[76.96.30.116]: Connection timed out (port 25)
> 
> Nov 17 21:36:26 penguin postfix/smtp[11362]: 39C27E7C517: 
> to=<XXXXXXXX at comcast.net>, relay=none, delay=60, status=deferred (connect to 
> mx1.comcast.net[76.96.62.116]: Connection timed out)
> 
> I used a dns tool to lookup comcast.net's dns info and it returned the 
> following which I thought was interesting...
> 
> mx1.comcast.net claims to be host IMTA05.westchester.pa.mail.comcast.net [but 
> that host is at 76.96.62.45 (may be cached), not 76.96.62.116]. 
> 
> mx2.comcast.net claims to be host IMTA22.emeryville.ca.mail.comcast.net [but 
> that host is at 76.96.30.39 (may be cached), not 76.96.30.116].
> 
> WTF!!!!
> 
> $ dig mx comcast.net
> ; <<>> DiG 9.3.3rc2 <<>> mx comcast.net
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41239
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4
> 
> ;; QUESTION SECTION:
> ;comcast.net.                   IN      MX
> 
> ;; ANSWER SECTION:
> comcast.net.            16      IN      MX      5 mx2.comcast.net.
> comcast.net.            16      IN      MX      5 mx1.comcast.net.
> 
> ;; AUTHORITY SECTION:
> comcast.net.            6389    IN      NS      dns102.comcast.net.
> comcast.net.            6389    IN      NS      dns101.comcast.net.
> 
> ;; ADDITIONAL SECTION:
> mx1.comcast.net.        6616    IN      A       76.96.62.116
> mx2.comcast.net.        7190    IN      A       76.96.30.116
> dns101.comcast.net.     147796  IN      A       68.87.64.204
> dns102.comcast.net.     153480  IN      A       68.87.66.204
> 
> 
> 

Possibly mx1 and mx2.comcast.net are load balanced based on location?  I
received an email from a friend that is located in Oregon with those
headers, however when I'm in Oregon and I get email from him I don't see
those specific headers in question.

emeryville.ca.mail.comcast.net

Both:

OMTA11.emeryville.ca.mail.comcast.net and
QMTA01.emeryville.ca.mail.comcast.net are in my headers suggest behind
the scenes location based routing.

I haven't, however been getting any timed out messages.  Anyone here
work for Comcast?

-- 
Don