sortofageek
Premium,Mod
join:2001-08-19
Valhalla Dr
clubs: |  reply to mbnva
(topic move) [Split] [E-mail] MS Hotmail Blocks Comcast Traffic
Moderator Action
The post that was here, and all followups to it, were moved to a new topic .. »[Split] [E-mail] MS Hotmail Blocks Comcast Traffic |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
| reply to jbob
Re: [E-mail] Microsoft Hotmail Blocks Comcast Traf
said by jbob  :You know if Comcast allows use of any alternate ports besides 25? I wonder if using an alternate port will also do the trick? They use port 465 as well. I tried both ports, with and without AUTH, and the mail was being rejected.
I just tested using rwcrmhc11, a server that was previously rejecting the hotmail-bound traffic, and it is working fine now.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
howardthebrit
| reply to jbob
I can confirm that an email that was stopped has now been sent as of 12/2 1:15PM EST.
I had asked for the issue to escalated to Comcast managers as I was not getting any useful status from Comcast. This was the reply:
Thank you for contacting Comcast. My name is Richard and I will be pleased to assist you today.
Re: What is the status with this issue? While the majority of issues can be addressed via email correspondence, we are unable to address this issue from within the email forum. Please contact our technical support group at 1-800-COMCAST for a more free flowing dialogue.
Translation - we have something to say to you that we are not comfortable putting in writing 
We can all read what we want into that - and no, I'll not waste any more of my time vainly pressing digits on my phone till the cows come home... |
|
djo165
join:2005-05-17
Prosper, TX |  reply to mbnva
Re: [E-mail] Microsoft Hotmail Blocks Comcast Traffic
As of noon on Friday, the email from Comcast to Hotmail/MSN seems to be working again. I've sent two emails to Hotmail accounts, and both got through okay. |
|
jbob
Reach Out and Touch Someone
Premium
join:2004-04-26
Little Rock, AR
 ·Comcast
·AT&T Southwest
2 edits | reply to NormanS
Re: [E-mail] Microsoft Hotmail Blocks Comcast Traf
They are saying now on the Comcast Forums that the blocks are starting to be removed from the smtp servers. Letting the mail trickle out now. It seems instead of removing all at once they're doing em a little at a time.
Won't do any good to test anymore!
And just read this on the Comcast Forums:
"Since I've had Comcast, I setup my Comcast e-mail so all e-mail sent to my comcast.net address gets forwarded to my hotmail.com address.
For the past few days, if anyone with a comcast.net address tried to send me an e-mail directly to my hotmail.com address, they'd get the 550 error. But, if they sent it to my comcast.net address, it would successfully get forwarded to my hotmail.com address. Strange, I think."
For crying out loud, another workaround! |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to jbob
said by jbob :You know if Comcast allows use of any alternate ports besides 25? I wonder if using an alternate port will also do the trick? Um. Yes. As I posted on 2005-11-30 19:14:22, on the third page of this thread. I used port 465 (with SSL) for sending a test email to an MSN Hotmail account. It depends upon which Comcast output SMTP server you draw in the lottery; my first attempt failed, as you can see in that post. See funchords posting about the one Comcast output server which appears not to be blocking email to the MSN MX servers. That server appears in the headers of my successful send.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
jbob
Reach Out and Touch Someone
Premium
join:2004-04-26
Little Rock, AR | reply to NormanS
You know if Comcast allows use of any alternate ports besides 25? I wonder if using an alternate port will also do the trick? |
|
jbob
Reach Out and Touch Someone
Premium
join:2004-04-26
Little Rock, AR
·Comcast
·AT&T Southwest
| reply to funchords
Jeesh then I wonder how many days it's really gonna take? lol
Luckily I use Yahoo for my smtp server. I don't see any of these Comcast issues. I also stopped using their DNS servers months ago. You know the old saying, fool me once, shame on you, fool me twice, shame on me.  |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
·Verizon Online DSL
·Skype
| reply to jbob
said by jbob :A little earlier some of the posters on those Comcast Forum threads were reporting that mail is now going to Hotmail from Comcast. Maybe the blocking has finally stopped. 220 comcast.net - Maillennium ESMTP/MULTIBOX rwcrmhc13 #91
MAIL FROM:<xxxxx@comcast.net>
250 ok
RCPT TO:<xxxxx@hotmail.com>
550 permit denied
Nope, still blocked. They must have hit the lucky #12 server in the rotation. I found it by repeatedly trying -- because I saw that once in a great while, the mail would actually go through.
Besides, don't you know that server misconfigurations take more than two full days for experienced, qualified engineers to fix?
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
jbob
Reach Out and Touch Someone
Premium
join:2004-04-26
Little Rock, AR | reply to NormanS
A little earlier some of the posters on those Comcast Forum threads were reporting that mail is now going to Hotmail from Comcast. Maybe the blocking has finally stopped. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
1 edit | reply to funchords
.jpg/thumb.jpg "73294 bytes")
Figure 1. |
said by funchords :said by NormanS :There appear to be a pair of IP addresses associated with that server: 12/01/05 20:06:16 dns rwcrmhc12.comcast.net
Canonical name: rwcrmhc12.comcast.net
Addresses:
216.148.227.85
216.148.227.152
.85 is the one that worked in my test. 216.148.227.152 doesn't answer at all. Hmmm. .125 works .152 doesn't Might be a coincidence or might be a typo. Has to be a typo within the system; that is a straight cut-and-paste from Sam Spade.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
·Verizon Online DSL
·Skype
| reply to NormanS
said by NormanS :There appear to be a pair of IP addresses associated with that server: 12/01/05 20:06:16 dns rwcrmhc12.comcast.net
Canonical name: rwcrmhc12.comcast.net
Addresses:
216.148.227.85
216.148.227.152
.85 is the one that worked in my test. 216.148.227.152 doesn't answer at all.
Hmmm.
.125 works
.152 doesn't
Might be a coincidence or might be a typo.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to funchords
There appear to be a pair of IP addresses associated with that server:
12/01/05 20:06:16 dns rwcrmhc12.comcast.net
Canonical name: rwcrmhc12.comcast.net
Addresses:
216.148.227.85
216.148.227.152
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
·Verizon Online DSL
·Skype
| reply to mbnva
Re: [E-mail] Microsoft Hotmail Blocks Comcast Traffic
** WORKAROUND **
Until they sort this out, you can use 216.148.227.125 in place of smtp.comcast.net for your outgoing mail. It isn't being blocked by Comcast -or- by Hotmail.
It identifies itself as rwcrmhc12 ... I think Comcast may have juggled their name and IP assignments and it has everything confused!
But if you don't trust me (and you shouldn't), you can verify that it's a legitimate Comcast server here:
»www.dnsstuff.com/tools/ptr.ch?ip···.227.125
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
LeftOfSanity
join:2005-11-06
Felton, DE
| reply to NormanS
Re: [E-mail] Microsoft Hotmail Blocks Comcast Traf
Norman,
May I ask what your profession is? You have an awful lot of knowledge about the intricacies of email. If not already, you should put it to good use. I know I am at least in awe of all your knowledge. (I need to goto email/spam school)
--
"I went to the park and saw a kid flying a kite. The kid was really excited. I don't know why, that's what they're supposed to do. Now if he had a chair on the other end of that string, I would have been impressed." -M.H. |
|
jbob
Reach Out and Touch Someone
Premium
join:2004-04-26
Little Rock, AR
·Comcast
·AT&T Southwest
3 edits | reply to NormanS
Actually here is the top part of the message I got:
Received: from mail-kr.bigfoot.com ([211.115.216.228])
by rwcrmxc15.comcast.net (rwcrmxc15) with SMTP
id 20051201191241r1500hr99je; Thu, 1 Dec 2005 19:12:41 +0000
X-Originating-IP: [211.115.216.228]
Date: Thu, 01 Dec 2005 14:12:41 -0500
From: Mail Delivery Subsystem MAILER-DAEMON@bigfoot.com
Message-Id: 0512011412_BFLITEMAIL-KR4_835539_18153422_1879@BFLITEMAIL-KR4.bigfoot.com
To: xxxxx@comcast.net
And while I'm at it how did you get your post to me to include the contents in between these symbols? Crap I can't get them to post. The greater than/less than symbols aboce the comma and period. When I copy and paste this mail stuff that info gets deleted from my post! lol |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to jbob
Actually, the Comcast notice tells you the reporting MTA, which is the one rejecting the email. If MRB was rejecting the message, the Bigfoot MTA should have sent the Delivery Failure Notice directly to whatever email account you gave them for notifications. Then you would have a DFN from Bigfoot, which identified the reporting MTA as a MRB server.
At least, I think that is what I am seeing. Or did the notice you cited not come from <MAILER-DAEMON@comcast.net>?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
jbob
Reach Out and Touch Someone
Premium
join:2004-04-26
Little Rock, AR
·Comcast
·AT&T Southwest
| reply to NormanS
Norman
What I did was send my test message through one of my Comcast accounts. One was to a Yahoo address, one to my MRB addy and one to my bigfoot addy. My bigfoot account is set to forward to three accounts.(Yahoo, MRB, and a Comcast acct) I guess it looks like MRB rejected the bigfoot email, which in turn was returned back to me with the error message. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to funchords
said by funchords :All, here's another test you can run. Beats me why Comcast and Hotmail's best can't figure this one out. It also means that, in a pinch, you can send mail to your hotmail friends. However, I'm 100% sure that hotmail will only accept hotmail-destined messages this way. Don't even try to relay through it -- you'll surely be banned. Hotmail uses mx1.hotmail.com through mx4.hotmail.com {Removed a bunch of example stuff} It works for MSN Hotmail because MSN apparently is not checking for dynamic host IP addresses; this will not work for AOL. It may not work if the Comcast dynamic IP address has gotten listed by whatever filters MSN uses. In theory, you could also add the MSN MX server to your mail client as the outgoing SMTP server; as long as your destination email address is in the @msn.com or @hotmail.com domains. The MSN MX servers will only accept email for those domains, so don't try to send email to any other domain from that account.
As an aside, the reason you get spam with a list of @comcast.com email addresses is because the spammer is using a proxy, not a mail server; the proxy can't do DNS lookups for MX servers, it can only connect directly to the destination MX server. MX servers are not relays, they only accept email for the domain that they serve. Works the same way as my description of setting up a mail client to send directly to the MSN MX servers.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to jbob
said by jbob :Hmmm after the test message I sent earlier I finally got a reject from a delivery to MyRealBox too: "The original message was received at Thu, 01 Dec 2005 13:59:48 -0500 EST from rwcrmhc12.comcast.net [216.148.227.89] The Comcast message submission server picking up your email...
----- The following addresses had permanent fatal errors -----
----- Transcript of session follows -----
>>> Connecting
553 Your site is blocked due to previous spamming incidents"
More:
Reporting-MTA: dns; bflitemail-kr4.bigfoot.com
Arrival-Date: Thu, 01 Dec 2005 13:59:48 -0500 EST
So does this mean that MyRealBox rejected my Comcast message to myself?
Um, MRB is using Bigfoot SMTP servers?(*) Well, yes, bflitemail-kr4.bigfoot.com rejected email from the Comcast MTA trying to deliver your message. Interesing; one of my Comcast correspondent's email messages got routed to my spam handling account. Partial headers:
Return-path: <%User_ID%@comcast.invalid>
Received: from sccrmhc12.comcast.net (204.127.202.56) by aosake.net (Mercury/32 v4.01b) with ESMTP ID MG000003;
30 Nov 2005 21:43:22 -0800
X-Blocked: Blocked by 'SPEWS (l1 SORBS) (Tag only)'
Received: from mycomputer (c-24-6-180-142.hsd1.ca.comcast.net[24.6.180.142])
by comcast.net (sccrmhc12) with SMTP
id <2005120105431301200ar7u0e>; Thu, 1 Dec 2005 05:43:17 +0000
Message-ID: <003401c5f63a$58c70060$0200a8c0@hsd1.ca.comcast.net>
{more stuff removed}
X-AC-Weight: [# ] -94
X-CC-Diagnostic:
Header Received matches "*[rsw][cs]crmhc1[1-4].comcast.net*" (-119),
Header X-Blocked matches "*SORBS*" (9),
Header X-Blocked matches "*SPEWS (l1 SORBS)*" (9), comcast.net (2),
Header "References" Exists (5)
Ah, I see. I still need to adjust my filters. The '-94' score should have bypassed the spam handling account; I have some other trigger that needs adjusting. I refer you to the regex line in the "Header Received" rule above; the Comcast server should have been white listed.
(*)Regarding that server which rejected the message; how are you routing email to your MRB account? My MRB test message looks thus:
{Removed stuff}
Return-Path: <tsudohnimu-*****@yahoo.com>
Received: from smtp21.mail.bbt.yahoo.co.jp not authenticated [202.93.85.136]
by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 1.6 $ on Linux;
Thu, 01 Dec 2005 17:41:09 -0700
Received: from unknown (HELO ?192.168.102.100?) (*?********@71.131.177.136 with plain)
by smtp21.mail.bbt.yahoo.co.jp with SMTP; 2 Dec 2005 00:41:08 -0000
X-Apparently-From: <%User_ID%@yahoo.co.jp.invalid>
Message-ID: <438F97E6.5000407@yahoo.com>
{Removed stuff}
To: %User_ID%@myrealbox.invalid
{Removed stuff}
Unless; are you using a Bigfoot account to forward email:
Return-path: <tsudohnimu-*****@yahoo.com>
{Removed stuff}
Received: from smtp22.mail.bbt.yahoo.co.jp ([202.93.85.137])
by BFLITEMAIL-KR2.bigfoot.com (LiteMail v3.03(BFLITEMAIL-KR2)) with SMTP id 0512012002_BFLITEMAIL-KR2_498525_16219083;
Thu, 01 Dec 2005 20:03:20 -0500 EST
Received: from unknown (HELO ?192.168.102.100?) (*?********@71.131.177.136 with plain)
by smtp22.mail.bbt.yahoo.co.jp with SMTP; 2 Dec 2005 01:03:19 -0000
X-Apparently-From: <%User_ID%@yahoo.co.jp.invalid>
Message-ID: <438F9D16.7000103@yahoo.com>
{Removed stuff}
To: %User_ID%@bigfoot.invalid
{Removed stuff}
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
