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)
getting these two error messages when sending to yahoo
1/11/2024 3:34:15 PM - Server at DS0PR14MB7526.namprd14.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
1/11/2024 3:24:36 PM - Server at PH0PR14MB6715.namprd14.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to ConnectionReset'
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.
I filed a support request with Microsoft.
FWIW, the support article mentioned (https://learn.microsoft.com/en-us/exchange/troubleshoot/email-delivery/send-receive-emails-socketerror) says to make registry changes on the on-prem server. I have no on-prem server. I'm connected directly to Office 365 for email services.
S**t! One of the changes we made to my account involved the SPF record, and now it's fixed. We also made changes to the DMARC records.
I like your theory of an enforcement change at Yahoo. Even so, refusing the socket hardly seems like the correct response to an SPF failure.
We have been experiencing the same issue. It is hindering our ability to communicate with our clients, therefore effecting our customer service standards. I am hoping there is a quick and easy solution.
Interesting. I've had this Office 365 account for a long time, at least 10 years, and I regularly email with yahoo.com accounts. I don't recall this kind of error being persistent before.
Apparently this is nothing new with Outlook vs Yahoo accounts. You can search and see that as far back as 2013 this has been an ongoing problem between them. I am not sure who is at fault here but it needs to be fixed. I pay way too much money for Office 365 and use the Outlook desktop version to deal with ongoing issues.