E-Mail and Xfinity Connect Help

[denvergail]

A friend and I (both of us with Comcast) depend upon receiving e-mail from another colleague with a different ISP. Neither the friend nor I (both on Comcast) are receiving ANY e-mail from the colleague. We stopped receiving e-mail from him on March 24. Prior to that date, there was no problem.

The missing e-mails are NOT in our spam folders, either on the server or on our computers. The colleague has contacted his ISP and the messages are NOT being bounced back. Using my alternate YAHOO e-mail address I am getting the e-mails that are not getting delivered via Comcast.

Any insight or directions that we need to follow to resolve?


Here is a successfully delivered e-mail header (prior to the failure to receive):

Received: from imta19.emeryville.ca.mail.comcast.net ([76.96.30.15]) by rwcrmxc12.comcast.net (rwcrmxc12) with ESMTP id 20080319171052r1200n9rore>; Wed, 19 Mar 2008 17:10:52 +0000
Received: from server1.iddhosting.com ([66.216.127.15]) by IMTA19.emeryville.ca.mail.comcast.net with comcast id 35Ap1Z01E0L3sQa0K00000; Wed, 19 Mar 2008 17:10:52 +0000
Received: (qmail 12195 invoked from network); 19 Mar 2008 10:10:49 -0700
Received: from p7-123.dsl.ecentral.com (HELO **bleep**P) (216.38.196.123) by server1.iddhosting.com with SMTP; 19 Mar 2008 10:10:48 -0700
X-Originating-Ip: [76.96.30.15]
X-Authority-Analysis: v=1.0 c=1 a=h/3OgBlTUNtYLOsiDvwUgQ==:17 a=TxztQpGXAAAA:8 a=s1xyF-UK7RMN43pwapsA:9 a=w0aAd-zTgzQSaPQG8VMsVGn5sHkA:4 a=DFxpUQUX75kA:10 a=nt4eZ0Djs2cA:10 a=WU9nQ1MBPWUA:10 a=A0yEja8irJoA:10 a=-ZQhYGXY2L8A:10 a=zIgPd2tkY_EDO1K5dM0A:9 a=xeTyBEwJydITAhXUvK4A:7 a=yuhk5IutpiNB2sBW0ujfwHrijxgA:4 a=c2J58mv9xREA:10 a=Tg0C1ogEE9kA:10 a=AfD3MYMu9mQA:10 a=goqMsvngdYVMJpsKJ1cA:9 a=wKbvbaRfYCKVaIy8MQ_Z8aDeJGUA:4 a=KQqxNPgzF0kA:10 a=bC4pTEGzVWIA:10 a=B7mKDxbqvL4NMZ_L:18
Message-Id: 008601c889e4$149ecf40$4200a8c0@**bleep**P>

[bigchris]

The IP of the server in your headers isn't blocked and has no history of ever being blocked. Can you post the headers from the successful yahoo delivery so we can see if they are the same?

[denvergail]

Thanks for the reply (wasn't expecting it so soon!).

Please keep in mind that prior to March 24, 2008, all the e-mails were successfully delivering to Comcast.

Thanks!

here is the header from the colleague's e-mail. It was sent to both Yahoo e-mail & Comcast. Came through to Yahoo only:


X-YahooFilteredBulk: 74.200.207.18
X-Originating-IP: [74.200.207.18]
Authentication-Results: mta229.mail.re4.yahoo.com from=sfrpr.com; domainkeys=neutral (no sig)
Received: from 74.200.207.18 (EHLO server1.iddhosting.com) (74.200.207.18) by mta229.mail.re4.yahoo.com with SMTP; Fri, 28 Mar 2008 08:26:23 -0700
Received: (qmail 28749 invoked from network); 28 Mar 2008 10:24:38 -0500
Received: from p7-123.dsl.ecentral.com (HELO **bleep**P) (216.38.196.123) by server1.iddhosting.com with SMTP; 28 Mar 2008 10:24:37 -0500

[bigchris]

So it looks like the earlier ones came from a different server.

On your first headers you can see the messages we coming from (in bold):

Received: from server1.iddhosting.com ([66.216.127.15]) by IMTA19.emeryville.ca.mail.comcast.net with comcast id 35Ap1Z01E0L3sQa0K00000; Wed, 19 Mar 2008 17:10:52 +0000

But on the recent ones they are coming from:

Received: from 74.200.207.18 (EHLO server1.iddhosting.com) (74.200.207.18) by mta229.mail.re4.yahoo.com with SMTP; Fri, 28 Mar 2008 08:26:23 -0700

So server1.iddhosting.com either changed addresses, or there's some goofy networking going on. (Steve Baker might have a good idea on this one if he's around).

I'll check tomorrow to see if that second IP is blocked and respond then. If it is blocked it would explain why they suddenly stopped coming.

[steve-baker]

---

bigchris wrote:
So it looks like the earlier ones came from a different server.

On your first headers you can see the messages we coming from (in bold):

Received: from server1.iddhosting.com ([66.216.127.15]) by IMTA19.emeryville.ca.mail.comcast.net with comcast id 35Ap1Z01E0L3sQa0K00000; Wed, 19 Mar 2008 17:10:52 +0000

But on the recent ones they are coming from:

Received: from 74.200.207.18 (EHLO server1.iddhosting.com) (74.200.207.18) by mta229.mail.re4.yahoo.com with SMTP; Fri, 28 Mar 2008 08:26:23 -0700

So server1.iddhosting.com either changed addresses, or there's some goofy networking going on. (Steve Baker might have a good idea on this one if he's around).

I'll check tomorrow to see if that second IP is blocked and respond then. If it is blocked it would explain why they suddenly stopped coming.

---

 Well, since you asked, my theory is that they simply moved from Rackspace to Fastservers.

[denvergail]

Got this from my colleague (the one on IDD's servers) late last night:

"I had a voice message a few minutes ago from the folks at IDD Webs. It appears that Comcast blocked their server IP for reasons unknown. So all should be fine now. I will spend the next hour figuring out to whom I sent email that clearly never arrived."



I received that message about 30 minutes after BigChris's reply. I began receiving his stale e-mails to my Comcast account within a few minutes after that (and took overnight to process them all through).


THANK YOU to whomever removed the block on that IP address.

[bigchris]

I'm glad it's fixed but I checked that IP above and it was never blocked. So perhaps they are sending from multiple IPs in the new location and a different one was blocked.

[denvergail]

Chris,

The e-mails that dumped through last night were dated from March 24 through March 31. They appear to have been in queue on the Comcast side since I was receiving them at my Yahoo account when they were originally sent. The e-mails that came through match the 2nd IP address I posted.

I don't really care which ISP was doing the blocking. But the finger-pointing is what I anticipated and dreaded. The timing was too coincidental from the time I posted the 2nd IP on this forum to the time I began receiving the stale e-mails (within an hour). We had spent many hours already dealing with ecentral/IDD without any success.

So, again, thank you for fixing the problem.

[bigchris]

I stand corrected!

I looked again and the server had been blocked since December and was unblocked last night, most likely due to a request from your hosting company. So, if you only were recently moved to this server, then you were unfortunately moved to a server that already was previously blocked.

The only reason you should be concerned about this is simply that if it's a shared host, it's possible it could happen again if the other users of it decide to spam Comcast. If however, the server is dedicated to you then you have much more control over that fate.