comcast.net mailservers - Page 2

me11ow · April 18th, 2008, 3:09 PM

A comcast tech over in their forums got it working for me, it was something in their settings. Try and see if it works for you now.

**Daniel** · April 18th, 2008, 3:37 PM

Hello,

We heard of multiple complaints associated with comcast and some other major providers who provide email services. After working with comcast on the problems, everything should now be fixed.

The issues boiled down to some discrepancies with DNS that should not cause any further issues such as this.

Thanks,

me11ow · April 18th, 2008, 3:56 PM

If you ask me this hush hush behind the scenes work on problems is a bit irritating. I have been spending MY time trying to track down this issue due to needing to get important emails to clients on comcast's network. I opened a ticket about this issue and it was left that it was comcast's fault and I would have to get them to fix it, so that is what I was doing. If I had prior knowledge that surpass was working in it with comcast I could have saved ALOT of time.

All I am asking is be upfront with your customers when there is a problem and say you will handle it.

**cowboy** · April 19th, 2008, 12:53 PM

All was looking OK last night and queue was empty, but, problem back again today.

Code:

Message 1JnFHV-00080j-3L is not frozen
delivering 1JnFHV-00080j-3L
Connecting to mx1.comcast.net [76.96.62.116]:25 ... connected
  SMTP<< 421 IMTA06.westchester.pa.mail.comcast.net comcast Reverse DNS failure : Try again later
  SMTP>> QUIT
LOG: MAIN
  SMTP error from remote mail server after initial connection: host mx1.comcast.net [76.96.62.116]: 421 IMTA06.westchester.pa.mail.comcast.net comcast Reverse DNS failure : Try again later
Connecting to mx2.comcast.net [76.96.30.116]:25 ... connected
  SMTP<< 421 IMTA11.emeryville.ca.mail.comcast.net comcast Reverse DNS failure : Try again later
  SMTP>> QUIT
LOG: MAIN
  SMTP error from remote mail server after initial connection: host mx2.comcast.net [76.96.30.116]: 421 IMTA11.emeryville.ca.mail.comcast.net comcast Reverse DNS failure : Try again later
LOG: MAIN
  == xxxx@comcast.net R=lookuphost T=remote_smtp defer (0): SMTP error from remote mail server after initial connection: host mx2.comcast.net [76.96.30.116]: 421 IMTA11.emeryville.ca.mail.comcast.net comcast Reverse DNS failure : Try again later

**Bigjohn** · April 20th, 2008, 3:03 PM

Hmm.
is it that SURPASS is not allowing the lookup? That their device is failing to lookup, or the DNS entries are incorrect on the servers that they're looking at?

**cowboy** · April 21st, 2008, 10:32 AM

I think it lies with the changes made last week in the DNS cluster, posted here: http://www.surmunity.com/announcemen...tml#post289122 , and because it began working for about 12 hours on Friday, following Daniel’s post above.

.

delphinium42 · April 21st, 2008, 4:42 PM

It is still not working for me. I can't get any email through to comast.net from my servers

**Bigjohn** · April 21st, 2008, 5:28 PM

Quote:

Originally Posted by delphinium42

It is still not working for me. I can't get any email through to comast.net from my servers

Have you checked your domain's dns?

try INTODNS.com

**cowboy** · April 21st, 2008, 5:56 PM

My reverse report from intodns.com:

Code:

Reverse MX A records (PTR)Your reverse (PTR) record:
71.90.29.72.in-addr.arpa ->  pine.arvadaweb.com
You have reverse (PTR) records for all your IPs, that is a good thing.

The problems all started last week when they worked on the DNS cluster.

.

April 20th, 2008, 3:03 PM	#14 (permalink)
Bigjohn minor deity Super #1 Joined in Apr 2004 Lives in Georgia Hosted on XEON 7,229 posts Gave thanks: 19 Thanked 91 times	Hmm. is it that SURPASS is not allowing the lookup? That their device is failing to lookup, or the DNS entries are incorrect on the servers that they're looking at? __________________ Proud to be a Surmunity Mod! XEON PASS60 PASS61 Make a fundamental difference! My Sites: Curious about Brewing Beer? Join the community! >>>>> Some Change is GOOD! Keep your paycheck! Support the Fair Tax Get into an Art museum Victorian London It's your brain -*ON WEB* - mybrainhost.com (under development) What SHOULD Government do? Much Less than it Does!

April 21st, 2008, 10:32 AM	#15 (permalink)
cowboy Surpass Fan Excelling Contributor Joined in Nov 2005 Lives in Colorado Hosted on DEDI 924 posts Gave thanks: 2 Thanked 91 times	I think it lies with the changes made last week in the DNS cluster, posted here: http://www.surmunity.com/announcemen...tml#post289122 , and because it began working for about 12 hours on Friday, following Daniel’s post above. . __________________ Where would you be if you were at the highest court in the land (US)?

April 21st, 2008, 5:56 PM	#18 (permalink)
cowboy Surpass Fan Excelling Contributor Joined in Nov 2005 Lives in Colorado Hosted on DEDI 924 posts Gave thanks: 2 Thanked 91 times	My reverse report from intodns.com: Code: Reverse MX A records (PTR)Your reverse (PTR) record: 71.90.29.72.in-addr.arpa -> pine.arvadaweb.com You have reverse (PTR) records for all your IPs, that is a good thing. The problems all started last week when they worked on the DNS cluster. . __________________ Where would you be if you were at the highest court in the land (US)?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Rate This Thread
Rate This Thread:

April 18th, 2008, 3:09 PM	#10 (permalink)
me11ow Registered User Fresh Surpasser Joined in May 2006 20 posts Gave thanks: 0 Thanked 0 times	A comcast tech over in their forums got it working for me, it was something in their settings. Try and see if it works for you now.

April 18th, 2008, 3:37 PM	#11 (permalink)
Daniel Sysadmin Seasoned Poster Joined in Feb 2005 71 posts Gave thanks: 0 Thanked 42 times	Hello, We heard of multiple complaints associated with comcast and some other major providers who provide email services. After working with comcast on the problems, everything should now be fixed. The issues boiled down to some discrepancies with DNS that should not cause any further issues such as this. Thanks,

April 18th, 2008, 3:56 PM	#12 (permalink)
me11ow Registered User Fresh Surpasser Joined in May 2006 20 posts Gave thanks: 0 Thanked 0 times	If you ask me this hush hush behind the scenes work on problems is a bit irritating. I have been spending MY time trying to track down this issue due to needing to get important emails to clients on comcast's network. I opened a ticket about this issue and it was left that it was comcast's fault and I would have to get them to fix it, so that is what I was doing. If I had prior knowledge that surpass was working in it with comcast I could have saved ALOT of time. All I am asking is be upfront with your customers when there is a problem and say you will handle it.

April 21st, 2008, 4:42 PM	#16 (permalink)
delphinium42 Registered User Fresh Surpasser Joined in Sep 2004 8 posts Gave thanks: 0 Thanked 0 times	It is still not working for me. I can't get any email through to comast.net from my servers

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)