This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Starting this week, our emails to yahoo and aol accounts are not being delivered, but emails to other email accounts are working. Here is one of the yahoo error message: 1/12/2024 9:27:16 PM - Server at SJ2PR02MB10076.namprd02.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 1/12/2024 9:26:15 PM - Server at mta5.am0.yahoodns.net (67.195.204.73) returned '421 4.4.2 Connection dropped due to SocketError'
And here is the aol error message: 1/12/2024 9:27:38 PM - Server at PH0PR02MB7367.namprd02.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
1/12/2024 9:15:15 PM - Server at mx-aol.mail.gm0.yahoodns.net (67.195.204.80) returned '421 4.4.2 Connection dropped due to SocketError'
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 12%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER6%3C/text%3E%3C/svg%3E)
Good point. I did not check his MX earlier.
It looks like they switch mail hosting company (from AWS to Microsoft) and there are old DNS records that should've been deleted but no one took care of it.
The domain for our emails is "@mcbc.org".
In addition to what Ron said, your MX records are also incorrect. Assuming your email is on M365 you need to make these changes -
MX LEAVE IN PLACE
0 mcbc-org.mail.protection.outlook.com
MX DELETE
10 mcbc.org
SPF (TXT) LEAVE IN PLACE
v=spf1 include:spf.protection.outlook.com -all
SPF (TXT) DELETE
v=spf1 ip4:69.90.163.40 +a +mx +include:spf.antispamcloud.com ~all
It looks like Google manages your DNS, so you must have your domain name in a google admin center someplace, that is where you would make these changes.
-Brad
The socket error mentioned is not a dns configuration issue.
It absolutely is., in the sense that yahoo is rejected the email because you don't have the correct anti-spam records setup in your domain's DNS.
-Brad
I won't say it is or isn't related. Fixing DNS records is a must. Many got their problem fixed by creating/correcting those DNS records. If the problem goes away, you've fixed it. If it does not, look at other possibilities.
The socket error mentioned is not a dns configuration issue.