said by Re: 550 permit denied error when sending email to MSN/Hotmail by jason1 :> BlueChip & others,
>
> As it has been stated by others above, Comcast is
> rejecting emails destined for the MSN/Hotmail domain
> at this time. So yes, the 550 Permit Denied message
> is coming from the Comcast server, not MSN/Hotmail.
>
>
> The reason these emails are currently being rejected
> is to keep this issue from affecting email delivery
> to other non-MSN/Hotmail domains. Once the issue is
> resolved and our engineers notice the current
> MSN/Hotmail email queue start to decrease, they will
> remove this block and start allowing email to be
> delivered to MSN/Hotmail.
Jason,
With respect, I'll believe it when I see MSN Hotmail post it on ~their~ status board. ( »
support.msn.com/networkstatusres···ocId=460 ) ... at the time of this posting, even after their furiously working on the problem for more than 24 hours, it still says
"The service is available; there are no known network issues at this time."I'm betting that's because there is no MSN Hotmail problem. Someone in the Comcast chain of command has explained this issue away without really checking, and Tech Support (in good faith) is just doing their job and telling the customers what they think is going on. But it's time for Tech Support to pick up the phone and say, "WTF!?"
If I'm wrong, and the 550 response
really is to shield Hotmail from a flood of mail, one of three things should happen:
- Comcast should accept the message and then send a Delivery Status Notification that delivery would be delayed. When service is restored, you can send to Hotmail in small bursts.
- Comcast should get a backup method from hotmail and use that until hotmail fixes the primary problem.
or
- Comcast should reject the message, but with a 450 or 452 temporarily rejected code, not a 550 permanently rejected code.
Please, no more explanations. This needs followup