Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Using Microsoft smtp.office365.com Server, Send fails to all accounts at Comcast.net

  • No replies
  • 3 have this problem
  • 1 view
more options

Using Thunderbird, When I send to someone@comcast.net, I get an error back after about 24 hours. Your message couldn't be delivered. Despite repeated attempts to contact the recipient's email system it didn't respond.

If I send a message using a Web based service or using my Cell Phone, there is no problem with Comcast.

Info from my Sys Admin:

2 messages that you sent that are listed as “Pending”.  Here is the information on the reason:

Reason: [{LED=421 4.2.0 service unavailable};{MSG=};{FQDN=mx1.comcast.net};{IP=96.114.157.80};{LRT=2/13/2018 8:51:11 PM}]. OutboundProxyTargetIP: 96.114.157.80. OutboundProxyTargetHostName: mx1.comcast.net

So, it does appear to be an issue with your setup rather than Comcast blocking our domain, for example.

Using Thunderbird, When I send to someone@comcast.net, I get an error back after about 24 hours. Your message couldn't be delivered. Despite repeated attempts to contact the recipient's email system it didn't respond. If I send a message using a Web based service or using my Cell Phone, there is no problem with Comcast. Info from my Sys Admin: 2 messages that you sent that are listed as “Pending”. Here is the information on the reason: Reason: [{LED=421 4.2.0 service unavailable};{MSG=};{FQDN=mx1.comcast.net};{IP=96.114.157.80};{LRT=2/13/2018 8:51:11 PM}]. OutboundProxyTargetIP: 96.114.157.80. OutboundProxyTargetHostName: mx1.comcast.net So, it does appear to be an issue with your setup rather than Comcast blocking our domain, for example.