steved13's profile

New Poster

 • 

3 Messages

Wednesday, January 3rd, 2024 3:43 AM

Closed

Server at mx1.mxge.comcast.net (2001:558:fd01:2bad::5) returned '421 4.4.2 Connection dropped due to SocketError'

Email sent from Microsoft 365 domain @hillsboropres.org to email addresses in the @comcast.net domain are never delivered. The error message returned to the @hillsboropres.org domain email related to my address is:

...@comcast.net
12/30/2023 4:16:18 AM - Server at BN0PR10MB5239.namprd10.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
12/30/2023 3:53:35 AM - Server at mx1.mxge.comcast.net (2001:558:fd01:2bad::5) returned '421 4.4.2 Connection dropped due to SocketError'

 This started happening intermittently several months ago (around oct-2023).

The problem has gotten to the point that no email from the @hillsboropres.org domain is delivered to any of the email addresses at @comcast.net.

Does anyone know how to fix this problem?

Official Employee

 • 

2.2K Messages

1 year ago

Thank you for reaching out to us @steved13! When taking a look online, it would seem this message 421 4.4.2 connection dropped due to SocketError might be linked to TLS 1.0 and 1.1. Have you tried reaching out to Microsoft 365?

New Poster

 • 

3 Messages

1 year ago

I have not received any replies to my question.

I have not talked to Microsoft 365 be cause this problem only affects @comcast.net email addresses.

Official Employee

 • 

2.2K Messages

When looking at some support articles online for this issue, it would seem a ticket needs to be opened for the Microsoft 365 email address or the TLS settings need to be updated within the Microsoft 365’s email settings @steved13.

 

 

For troubleshooting purposes, are any of the Comcast email addresses that are not receiving the emails sent by the Microsoft 365 account, Comcast email addresses that are yours?

 

We can definitely troubleshoot issues with not receiving the emails if you have access to any of the impacted Comcast email addresses. Although, this issue appears to require assistance from Microsoft 365 based on the support articles I am seeing for the error messages you are receiving.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

8 Messages

1 year ago

We are having this issue with Comcast now also.

From a Microsoft Exchange 365 email server (church email) to parishioners only the ones using Comcast/Xfinity email addresses.

specifically comcast.net email addresses.

Our error is across the board for ALL the comcast.net email recipients. 

:::ERROR EXAMPLE START:::

<user>@comcast.net
1/17/2024 7:57:42 PM - Server at XXXXXX<obscured>.NAMPXXX.PROD.OUTLOOK.COM returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
1/17/2024 7:41:35 PM - Server at mx2.mxge.comcast.net (2001:558:fd01:2bad::4) returned '421 4.4.2 Connection dropped due to SocketError'
:::ERROR EXAMPLE END:::

If you continue to blame Microsoft you will get nowhere. Fix your servers Comcast/Xfinity. This is just silly.

The servers for the church are setup properly. We are not seeing this from Google, Yahoo, AOL or any other servers, just Comcast/Xfinity.

Booooooooo!

Official Employee

 • 

905 Messages

1 year ago

I haven't seen this error reported in the context of IPv4, only IPv6.  We receive a lot of email over IPv6 from Microsoft and Google, I'll reach out to both and see if they're seeing similar activity.  We've been accepting mail over IPv6 for 10 years or so, and I don't recall seeing an issue like this.

8 Messages

I've run the test for our server here: https://testconnectivity.microsoft.com/tests/O365ExchangeDns/input and it passes with flying colors. We don't have any issues with DKIM, SPF or DMARC. Everything has been tripled checked this AM. The office is sending to a total of SIX Comcast.net email addresses in the weekly email. This is how they have been doing it for years. There are other recipients in this email as well. I can see how it might be possibly viewed as SPAM but in this case it is rejected by the Comcast/Xfinity server altogether. If you can get this working we would all greatly appreciate it. Otherwise we will just have to tell parishioners that we cannot send email to them if they have a Comcast.net address. Thank you. 

(edited)

Official Employee

 • 

2.2K Messages

Hi, @gjames50. I appreciate you circling back. I understand you've had some trouble as well. I see @XfinityAlex provided some feedback, and they are certainly an expert in this area. I see they are checking on this further and I would allow them more time to give you any information they find. You can also visit this link https://spa.xfinity.com/postmaster?faq=avoid-blocks-ipv4 for further assistance. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

7 Messages

1 year ago

Another faith organization here.  Experiencing this issue also, have checked MXtoolbox, M365 connection tests, etc.  It is not 100% of comcast.net emails, individual mails have no problem, messages sent to 10+ comcast.net addresses are the only mails not getting consistently delivered.  522 delivered, 78 failed, 62 pending (will fail w/in 24 hours), and 13 resolved.  The fails are in 5 email subjects, and some comcast.net customers are receiving it.  Furthermore, if the message that was not received is fwd'd to a single address that didn't get it: it is delivered.  I don't think this is a DNS record or mail setting, which I've checked, double-checked, and triple-checked.

Called Comcast, was told I had to be a customer receiving the message in order to talk to a person.  

This also doesn't match documented error codes:
https://www.xfinity.com/support/articles/email-errors




8 Messages

1 year ago

@XfinityAlex We are still having the issue. 

Error: ‎550 5.4.300 Message expired -> 451 4.2.0 Throttled - https://postmaster.comcast.net/smtp-error-codes.php#RL000010‎

All Comcast.net emails Failed Delivery

Email sent on 02/07/2024

So, it's still broken. Everything on our end checks out. 

There are six email addresses that are comcast.net addresses. Every one of them has this failure. As I stated before, no other emails sent to other domain servers failed, just comcast (e.g. Gmail, Yahoo, Springmail, CenturyLink, Outlook, SBCglobal, Aol, Sprintmail, etc. all show Delivered).

Your servers are messed up. 

Thank you.

(edited)

Official Employee

 • 

905 Messages

@gjames50 Send me a DM with the domain of the sending messages.  This shouldn't still be happening.  Thanks

Official Employee

 • 

3.3K Messages

@gjames50 Thank you for confirming the issue is still ongoing. At this time I would recommend contacting our Xfinity Customer Security Assurance team, they would be the best team to assist you with finding a resolution. You can contact them by calling 1-888-565-4329, they are available from 8 AM - 12 AM EST, 7 days a week.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

2 Messages

@gjames50​ Our domain also experiencing this, and it appears to have started in the last two months. We are using O365 for our organization and emails to only @comcast.net accounts bounce back. Looks to be exactly the same issue, eager to understand what the problem is.

2/8/2024 5:35:18 PM - Server at <REDACTED>.namprd12.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
2/8/2024 5:20:40 PM - Server at mx1.mxge.comcast.net (2001:558:fd00:4f::4) returned '421 4.4.2 Connection dropped due to SocketError'

(edited)

2 Messages

@XfinityBillie​ I just called this number. The support technician said that sending to @comcast.net accounts requires them to be individually enumerated on emails now (no longer able to have them as part of a group). 

That seems like a somewhat daft policy...

Official Employee

 • 

376 Messages

Hello @Bargainville! I'd be happy to look further into this issue for you. Please send us a direct message with your first/last name and full address. You can start by clicking the "direct message" icon on the upper right page of the forum page. Once you click on that, input our shared handle "Xfinity Support" to send us a direct message. If you're signed in to your forums profile and because you have already posted to the public page, you should have the option to do so.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here