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.
Larry,
Did you have Microsoft tech support contact you? I have sent over a ticket and they are setting up a time to talk with me and work on the issue. All of my emails to yahoo and aol are still bouncing back to me. I have tried plain text everything. Nothing is working.
Louise
I opened a ticket and someone called
I have the same problem, email from my outlook business account cannot send to my customer yahoo email account, started Jan 16, I have to use my gmail to circumvent this.... not cool when you are paying by the month. Did AOL have a fight with microsoft or something? Better fix your problem
Yep, still as of today 1/18/2024
OK, well I filed a ticket, someone got through to me, we made some changes to the DNS records at my domain registrar (Google Domains, which was sold to Squarespace but still seems to be Google). The problem went away. It seems to me that the solution really couldn't have affected the problem, but the problem went away in any event.
Have you created a support ticket with Microsoft?