emails are bouncing back when sending to yahoo

Anonymous
2024-01-11T22:32:07+00:00

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'

Outlook | Windows | Classic Outlook for Windows | For home

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.

0 comments No comments

77 answers

Sort by: Most helpful
  1. Anonymous
    2024-01-26T14:25:19+00:00

    I guarantee you that they are getting a lot of support calls about this and will know what to do.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-01-26T14:14:56+00:00

    Thats good to know as my domain provider is also GoDaddy.

    thanks

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-01-26T13:48:54+00:00

    If your email provider is not also your DNS provider (as was my case), then your email service provider will not be able to help, except perhaps to tell you what DNS changes you need to make.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-01-26T13:41:25+00:00

    Hi Darren

    I've had DNS issues before with google / gmail. And like you tried to fix it myself. Never again.

    Since it appears to be a DNS issue, I will head over to my email service provider and put in a request for help.

    Thanks for the advice.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-01-26T12:10:27+00:00

    I went through a support ticket with Microsoft, and the problem was resolved. I understand why, and it's not that complicated.

    Yahoo and certain other email providers have started or are about to enforce a rule that sending domains (domains, not email providers) have a valid SPF record. They are also claiming to require DMARC and DKIM, but the real issue for now seems to be SPF. See https://www.proofpoint.com/us/blog/email-and-cloud-threats/google-and-yahoo-set-new-email-authentication-requirements for details.

    In my case, my email provider is Microsoft, but my domain registrar is Google. It is at the Google Domains DNS that we made the change. My SPF record had a stupid error in it that I should have seen myself. It's common for domains to have more than one SPF record, so it must be changed if that is the case with yours.

    I do wish that a more informative error message was used than the failed socket, but this seems to be the source of the problem.

    If you don't know your way around DNS, then, as the user to whom I'm replying says, you can seriously bork all your systems. Have a qualified admin do it, or ask Microsoft support for help.

    Was this answer helpful?

    0 comments No comments