  Rick C
@comcast.net | reply to NormanS Re: [E-mail] Microsoft Hotmail Blocks Comcast Traf
This issue has not been resolved. I still cannot send to a hotmail account without getting that error message.
Rick |
|
 NormanS Premium,MVM join:2001-02-14 San Jose, CA
·Pacific Bell - SBC
| reply to MarkinFL
 Figure 1. |
said by MarkinFL :
I have been having the same problem for over a month and half. I am getting upset. I can't get email to business clients that have @hotmail.com. Then of course there is the NOT RELIABLE @AOL.com they don't even let you know they did not handle it...the sender or receiver knows nothing AOL simply deletes it in cyberspace... I have been using email since we had a Microsoft mail server. The last 3 years have been the worst...its getting to the point I have to call and verify if clients receive. This is crazy. This is the result of defensive measures being taken against spam. If we would just have accepted spam, without trying to do more than just delete it, the spammers wouldn't be taking all the measures that they do to defeat filters, and blocks.
AOL is interesting. They do have a response when I try to run an SMTP verify with Sam Spade:
11/30/05 09:47:06 SMTP Verify %User_ID%@aol.invalid, at mailin-04.mx.aol.com Contacting 64.12.138.89 554- (RTR:BB) http://postmaster.info.aol.com/errors/554rtrbb.html HELO aosake.net 554- AOL does not accept e-mail transactions from dynamic or residential 554- IP addresses. 554 Connecting IP: 71.131.210.202 Doesn't want to talk to us But also see Figure 1. The screen shot is depicting an attempt to send email "end-to-end; directly from my DSL connection to the AOL MX server. I let it run for about an hour. The message was still in my MTA queue when I gave up. I don't normally run the "End-to-end" client, and I wanted to return the MTA to my usual configuration; relaying through my SBC SMTP server. Had I let that remain for several more hours, my MTA would have, eventually, given up and posted a "Delivery Failure Notice" to the sending account.
That isn't testing a regular ISP SMTP server, though. I have already demonstrated an issue with the Comcast output server, "sccrmhc11.comcast.net (63.240.77.81)", which won't answer to a DNS lookup with its name. Comcast needs to address that issue.
-- 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 howardthebrit One workaround: use gmail to send mail only
said by howardthebrit :
I'm getting the same problem all today: The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was 'namedeleted@hotmail.com'. Subject 'Answers', Account: 'mail.comcast.net', Server: 'smtp.comcast.net', Protocol: SMTP, Server Response: '550 permit denied', Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79 But I didn't have the problem with the same address just yesterday. Thanks to this forum I can see the ball is in Comcast's court...heaven help us. Actually, the ball is in hotmail's / msn's court. The receiving smtp server has the overzealous rule.
As a work around, I can send all my mail through my gmail.com account.
You need to have a working gmail account, and you need to edit its settings to allow pop3 access (even though you're not going to access it.)
Edit your existing Comcast account profile in your pop3 client (such as Outlook). Change the outgoing e-mail server to smtp.gmail.com port 465 (Outlook users will need the advanced tab to set the port). Enable that your outgoing server requires Authentication and enter your gmail username and password there.
From that point on, your incoming mail still comes from Comcast, but your outgoing mail goes through Gmail. -- 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
| said by funchords :Actually, the ball is in hotmail's / msn's court. The receiving smtp server has the overzealous rule. Really. Overzealous. Well, let me look at my MTA logs:
T 20051130 002239 438c26b3 Connection from 63.245.72.124 T 20051130 002241 438c26b3 HELO 71.131.210.202 E 20051130 002241 438c26b3 554 Misconfigured host; see: HTTP://antispam.aosake.net. T 20051130 002244 438c26b3 Connection closed with 63.245.72.124, 5 sec. elapsed. RFC 2821 requires the SMTP client connecting to an MX server to issue a HELO command with a machine identifier. An FQDN (Fully Qualified Domain Name) is preferred, but anything at all is acceptable for the RFC; including a "domain literal" (IP address). The theory is to identify the source machine. In the case of this reject, my MTA received a connection attempt from a machine at IP address 63.245.72.124, but that machine said, "HELO 71.131.210.202". Not only is the SMTP client mis-identifying itself, the HELO command is using my MTA's IP address as the domain literal. Technically, it is RFC 2821 compliant, and I should accept the connection. However, in my "overzealous" desire to prevent spam, I have a rule which regards an SMTP client identifying itself with my MTA's IP address as persona non grata; I reject that connection.
Some MX servers go an extra step, and run a DNS lookup on the IP address. Had I done so, I would have seen:
11/30/05 11:56:51 dns 63.245.72.124 nslookup 63.245.72.124 No reverse DNS (WSANO_DATA) Some MX servers, seeing "No reverse DNS" on a DNS lookup will assume that this is not an SMTP client that they want to hear from, and will reject the message on that ground. Here is another; same thing:
T 20051130 013246 438c26b9 Connection from 211.222.116.210 T 20051130 013247 438c26b9 HELO 71.131.210.202 E 20051130 013247 438c26b9 554 Misconfigured host; see: HTTP://antispam.aosake.net. T 20051130 013247 438c26b9 Connection closed with 211.222.116.210, 1 sec. elapsed. DNS lookup on the IP address:
11/30/05 12:08:12 dns 211.222.116.210 nslookup 211.222.116.210 No reverse DNS (WSANO_DATA) Then there is this example:
T 20051130 110146 438d8507 Connection from 200.164.81.246 T 20051130 110146 438d8507 HELO localhost E 20051130 110146 438d8507 554 Invalid host name; see: HTTP://antispam.aosake.net. T 20051130 110147 438d8507 Connection closed with 200.164.81.246, 1 sec. elapsed. E 20051130 110147 0 Connection from 200.164.81.246 refused because of short-term restriction. E 20051130 110148 0 Connection from 200.164.81.246 refused because of short-term restriction. In this case, the SMTP client issued "HELO localhost". There is no way for a remote machine to be "localhost"; that is the local connection, not a remote connection. So I test for it, and reject it. Overzealous rule? I think not. Here is the DNS lookup:
11/30/05 12:10:30 dns 200.164.81.246 nslookup 200.164.81.246 No reverse DNS (WSANO_DATA) It doesn't take long to figure out that a lot of spam is being sent from IP address sources with either no rDNS name, or an rDNS name indicating a dynamic host. So MX administrators who want to minimize spam received will test for this kind of connection.
Now, review my post concerning the Comcast SMTP output server, "sccrmhc11.comcast.net (63.240.77.81)". There is no rDNS for that IP address. Since a fair percentage of spam originates from such IP addresses, and there is no way to verify that the machine saying "HELO sccrmhc11.comcast.net" is even a Comcast mail server, MSN Hotmail is within their rights to refuse connections from that machine.
For the record, Sam Spade says this about that IP address:
11/30/05 12:15:53 dns 63.240.77.81 nslookup 63.240.77.81 Canonical name: sccrmhc11.comcast.net Addresses: 63.240.77.81 Whoa. Just two hours ago that IP address had no rDNS name.
Anyway, my point is this: Given the nature of spam source IP addresses, mail administrators of MX servers are within their rights to refuse connections from IP addresses when they can't verify that the connecting machine is who it claims to be. You may think that is being overzealous, but you can fix your SMTP output server so it doesn't fail against such tests.
AOL refuses connections from SMTP output servers on residential dynamic IP addresses. I can't relay mail from my computer to an AOL MX server through my MTA. I fix that by relaying through my ISP's MTA. My SMTP output server goes through an SBC authenticating SMTP server. Oh, BTW; that is within the SBC Yahoo! AUP/TOS.
-- 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
| I asked the question about port 25 blocks on the Comcast Forums and this was the answer I got back:
"At this time, there are no plans to implement a port 25 block across the network. This decision may change in the future but for now there are no plans. We do have a team investigating techniques to help reduce spam without having to block entire ports or other services." |
|
 NormanS Premium,MVM join:2001-02-14 San Jose, CA
·Pacific Bell - SBC
| said by jbob :I asked the question about port 25 blocks on the Comcast Forums and this was the answer I got back: "At this time, there are no plans to implement a port 25 block across the network. This decision may change in the future but for now there are no plans. We do have a team investigating techniques to help reduce spam without having to block entire ports or other services." I think the issue isn't that Comcast is blocking port 25, rather, that MSN Hotmail is refusing connection from some Comcast SMTP output servers. That is a matter for Comcast and MSN mail administrators to hash out. -- 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
| Well yeah, guess I should have responded to the thread instead of just to you. I think the original topic was because of a Spamming Comcast server. Although the current issue is with a misconfigured smtp server the port 25 blocks were discussed earlier in the thread. |
|
 NormanS Premium,MVM join:2001-02-14 San Jose, CA
·Pacific Bell - SBC
| said by jbob :Well yeah, guess I should have responded to the thread instead of just to you. I think the original topic was because of a Spamming Comcast server. Although the current issue is with a misconfigured smtp server the port 25 blocks were discussed earlier in the thread. Actually, it was a misconfigured Comcast server; MSN Hotmail is(was) rejecting email from Comcast output SMTP servers for lack of rDNS names. It appears that Comcast has finally addressed that problem.
I had forgotten that port 25 blocking had popped up as a side issue; and I even posted my thoughts on that matter. -- 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 | Jeesh you're right. Ok too many Comcast threads now. Well I know I read one where a blacklisted Comcast server was the issue. It was either here or GRC! lol Anyway I like your inputs. I learn much from them. |
|
  nakedland
join:2002-05-18 Friday Harbor, WA
·Comcast
·Verizon Online DSL
·Comcast Formerly ..
| reply to NormanS I have relatives who use MSN as their ISP and we seem to run across this problem about once a month. The email we're sending to them just sits in the outbox until both decide we can play together.  -- "My son defends our freedom in the USAF" |
|
  howardthebrit
| reply to NormanS Well you have me convinced about the misconfigured server, but there must be something else as well, because I still have the problem.
This is the official response from Comcast:
Thank you for your message concerning your Comcast e-mail service, my name is Susanne.
Emails sent from Comcast.net subscribers to MSN or Hotmail.com email accounts will be denied and the subscriber will receive the error "550 permit denied". This is caused by a problem on Microsoft's end caused by a virus. Microsoft is actively working to correct the issue. No ETC was supplied.
To assure the proper tracking of this issue, we have created the following customer service ticket: xxxxx
Please refer to this number should you contact us regarding this same issue.
Thank you for choosing Comcast.
So there we have it - "Not me sir, its a virus that's attacking them" |
|
  AnonComcastUser
@comcast.net
| I was able to email to a hotmail address from my Motorola RAZR on Cingular. The email address on that phone is xxxxx@comcast.net . The email worked. The party I emailed responded and I replied through Outlook. That email failed - 550 permit denied. Leads me to conclude its a Comcast internal problem, Hotmail's not at fault. |
|
 Nadude
join:2001-02-28 Bel Air, MD
1 edit | WOW....I knew if i came here i would find something....I just started having this issue like 15 minutes ago....LOL
While on the subject of email....Among the other threads with connectivity being in the toilet and TRACERT showing "ATT" routers screwing everything up, is anyone noticing a problem with COMCAST's smtp mail server??...I have a feeling it may be related...If i try and send an attachment it tales like forever if at all to send even the smallest attachment.....Hell just sending a REPLY it takes like a minute to send it if i dont get a SMTP TIMED OUT error....I can receieve email as fast as light but forget trying to send anything....Comcast told me it was an Outlook EXpress issue......Yeah right....Anyone else having this issue that could at least confirm i'm not the only one????
I'm in HArford County, MD and the speeds are going into the toilet!!! |
|
  funchords Hello Premium,MVM join:2001-03-11 Washington, DC
·Verizon Online DSL
·Skype
| reply to NormanS
said by NormanS :Well, let me look at my MTA logs: T 20051130 002239 438c26b3 Connection from 63.245.72.124 T 20051130 002241 438c26b3 HELO 71.131.210.202 Excellent post! Yes, I can't blame anyone who rejects this mismatch. If that isn't spamsign, I don't know what is! I take it back. This is Comcast's to fix. -- Robb Topolski -= funchords.com =- Hillsboro, Oregon USA ~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
 fullman
join:2001-12-30 Fort Lauderdale, FL
| reply to mbnva Re: [E-mail] Microsoft Hotmail Blocks Comcast Traffic
Sorry to throw a bone in here, but it doesn't seem to be Hotmail, rather Comcast.
Recently, mail sent from Comcast's mail servers to my personal dedicated server for multiple domains comes back instantly, saying the server cannot be found, while Hotmail, Gmail, Yahoo and other services and servers work without issue.
So, having said that, I believe Comcast is having issues. |
|
  funchords Hello Premium,MVM join:2001-03-11 Washington, DC
·Verizon Online DSL
·Skype
| reply to Nadude Re: One workaround: use gmail to send mail only
said by Nadude :is anyone noticing a problem with COMCAST's smtp mail server??...I have a feeling it may be related...If i try and send an attachment it tales like forever if at all to send even the smallest attachment.....Hell just sending a REPLY it takes like a minute to send it if i dont get a SMTP TIMED OUT error....I can receieve email as fast as light but forget trying to send anything....Comcast told me it was an Outlook EXpress issue......Yeah right....Anyone else having this issue that could at least confirm i'm not the only one???? You're not the only one. If you've ever tried an SMTP session in Telnet, you'll see that Comcast's servers sometimes take 30-45 seconds to respond to the previous command. Sometimes, it is fine.
You can set your server timeout to up to two minutes with no downside. There should be a setting for this in Outlook Express. -- Robb Topolski -= funchords.com =- Hillsboro, Oregon USA ~ Keeper of the D-Link FAQ ~ Did you Search? ~ More features, Free! Join BBR! ~ |
|
 Nadude
join:2001-02-28 Bel Air, MD
| said by funchords :said by Nadude :is anyone noticing a problem with COMCAST's smtp mail server??...I have a feeling it may be related...If i try and send an attachment it tales like forever if at all to send even the smallest attachment.....Hell just sending a REPLY it takes like a minute to send it if i dont get a SMTP TIMED OUT error....I can receieve email as fast as light but forget trying to send anything....Comcast told me it was an Outlook EXpress issue......Yeah right....Anyone else having this issue that could at least confirm i'm not the only one???? You're not the only one. If you've ever tried an SMTP session in Telnet, you'll see that Comcast's servers sometimes take 30-45 seconds to respond to the previous command. Sometimes, it is fine. You can set your server timeout to up to two minutes with no downside. There should be a setting for this in Outlook Express. Beat ya too it!!!...Actually i am trying the 5 minute mark..
Thank you for comfirming....I have been running AV, and Spyware going crazy wondering if it was my machine...LOL At least now i have something to go back to Comcrap with..
I'll give it some more time before going ballistic on them...I already have an 80.00 credit from them for poor service, maybe i'll try for more.....LOL |
|
  funchords Hello Premium,MVM join:2001-03-11 Washington, DC
·Verizon Online DSL
·Skype
| reply to mbnva Tested: This is COMCAST's problem
I ran a telnet session and was able to confirm that this is comcast's problem. This is not a bounce from hotmail -- hotmail is not even being contacted!
Here's how to try it (you input the part in bold):
c:\>telnet smtp.comcast.net smtp
220 comcast.net - Maillennium ESMTP/MULTIBOX sccrmhc12 #110 HELO comcast.net 250 comcast.net MAIL FROM:<yourname@comcast.net> 250 ok RCPT TO:<yourfriend@hotmail.com> 550 permit denied quit 221 comcast.net
Connection to host lost. -- 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 howardthebrit Re: One workaround: use gmail to send mail only
said by howardthebrit :
Well you have me convinced about the misconfigured server, but there must be something else as well, because I still have the problem.
This is the official response from Comcast:
Thank you for your message concerning your Comcast e-mail service, my name is Susanne.
Emails sent from Comcast.net subscribers to MSN or Hotmail.com email accounts will be denied and the subscriber will receive the error "550 permit denied". This is caused by a problem on Microsoft's end caused by a virus. Microsoft is actively working to correct the issue. No ETC was supplied.
To assure the proper tracking of this issue, we have created the following customer service ticket: xxxxx
Please refer to this number should you contact us regarding this same issue.
Thank you for choosing Comcast.
So there we have it - "Not me sir, its a virus that's attacking them" Hmmm. I guess that there are two problems. The post which got this thread started wasn't clear on the source of the error, but a later post offered this:
Reporting-MTA: dns; comcast.net Arrival-Date: 19 Oct 2005 17:46:23 +0000
Final-Recipient: rfc822; Action: failed Status: 5.1.0 MAIL FROM: 553 REPLY: 553_sorry,_your_mail_from_a_host_[63.240.77.84]_without_valid_reverse_DNS_was_administratively_denied_(#5.7.1) Diagnostic-Code: smtp; Permanent Failure: Other address status Last-Attempt-Date: Wed, 19 Oct 2005 17:48:21 -0000 That is clearly a Comcast server with no rDNS configured. I was able to prove that earlier by using Sam Spade to check the rDNS name on a Comcast output SMTP server, and there was no rDNS reported. About two hours later, there was an rDNS name on that server.
So, just now, I did a rare thing. I don't do this often because it is an abuse of my niece's trust; but I had to see just what was happening. I fired up MS Outlook Express (because it is easiest to change server configuration on the fly), and plugged in her Comcast account information. My first attempt to send an email to one of my MSN Hotmail accounts failed:
The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was '%User1_ID%@hotmail.invalid'. Subject 'Server test.', Account: 'SMTP Test', Server: 'smtp.comcast.net', Protocol: SMTP, Server Response: '550 permit denied', Port: 465, Secure(SSL): Yes, Server Error: 550, Error Number: 0x800CCC79 But that is not a Delivery Failure Notice from an MTA, as were the two cited early in this thread. It is the Comcast SMTP submission server refusing to even accept the message for delivery. Comcast is not saying any more than "550 permit denied". I have to wonder if this is due to the Comcast server being configured to refuse email with a Hotmail account as a destination. This is definitely not a Hotmail problem; Comcast isn't even trying to deliver this message, it is refusing to accept the message for delivery.
I still had the message in my outbox, so I opened it up to edit the recipient list. I changed the Hotmail account, and added a non Hotmail account, then resent the message. The second attempt went through. I can't seem to find the Hotmail Beta configuration to get at the full headers, though. So all I can get from the Hotmail account is this:
Proper Name (%User_ID%@gmail.invalid) To: "Proper Name" <%User2_ID%@hotmail.invalid> Cc: %User2_ID%@netscape.invalid Subject: Server test.
This is just the latest Comcast SMTP server test. However, I can get to the full headers from the Netscape account:
Return-Path: <%User_ID%@gmail.invalid> Received: from rly-na05.mx.aol.com (rly-na05.mail.aol.com [172.18.151.234]) by air-na04.mail.aol.com (v107.13) with ESMTP id MAILINNA41-2d25438e590f232; Wed, 30 Nov 2005 20:59:43 -0500 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by rly-na05.mx.aol.com (v107.13) with ESMTP id MAILRELAYINNA510-3c438e590d50; Wed, 30 Nov 2005 20:59:42 -0500 Received: from megumi (adsl-71-131-210-202.dsl.sntc01.pacbell.net[71.131.210.202]) by comcast.net (rwcrmhc12) with SMTP id <2005120101593801400i0q9de>; Thu, 1 Dec 2005 01:59:38 +0000 Message-ID: <001101c5f61a$dfa8ee60$6466a8c0@aosake.net> Reply-To: "Proper Name" <silly.kid@playhouse.invalid> From: "Proper Name" <%User_ID%@gmail.invalid> To: "Proper Name" <%User2_ID%@hotmail.invalid> Cc: <%User2_ID%@netscape.invalid> Subject: Server test. Date: Wed, 30 Nov 2005 17:59:19 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C5F5D7.C945DD60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-AOL-IP: 172.18.151.234 Clearly, some email with Hotmail addresses is not only being accepted by Comcast for delivery, but actually being delivered. Of course, this may have gone to a different server in the Comcast SMTP server farm. Which Comcast server you will get is a crap shoot. And the fact that I used port 465, to evade the SBC port 25 block, may also affect which Comcast SMTP server is used. Whatever Comcast reps are saying, I am seeing a problem with the Comcast SMTP servers.
P.S. No Comcast email address was needed for this, due to the nature of the Comcast servers. I want to stress, for the sake of my niece, and her parents, to the Comcast staff who may see this, that I do not use the Comcast servers; I only did this specifically to try and see what is going on. For my regular email smtpauth.sbcglobal.net is good enough; or I can use a couple of other SMTP servers where I have authorization as a user. Except for the occasional problem with AOL blocking it; so you Comcast folk are not alone in these ISP pissing matches over SMTP servers being blocked!
-- 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 | Could this actually be an issue with Comcast because much of their email not being sent is now filling up and causing a traffic jam so they just reject all mail now? |
|