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

77 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-01-18T12:05:14+00:00

    Yes, I did file a ticket and they should be calling me today. My concern now is will all of my agents need a ticket or will fixing the domain server be the fix for the entire agency. My domain is through Go Daddy.

    Honestly, Microsoft needs to be a "broken record" and keep reply to all post that you need to have the admin file a ticket. This would resolve the issue for everyone a lot quicker than just allowing people to post.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-01-18T12:37:45+00:00

    Whoeverworks with support may have to make changes to DNS or somethinglike that so yeah, it El need to be someone with admin privileges

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-01-18T14:48:43+00:00

    I might have got this fixed. I found a second SPF record in DNS -- that's Sender Policy Framework, not Sun Protection Factor :-)

    There must be only one. In my case the first record was created about 10 years ago when we used a different service. That was abandoned about 5 years ago but nobody thought or new to remove the old record when they created the one for Microsoft 365. My guess is that Yahoo has made a change to more strictly enforce SPF. If you have more than one SPF record then the check will fail and your messages will bounce.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-01-18T14:56:48+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-01-18T14:57:16+00:00

    we got the problem resolved. Microsoft had us update the SPF, DKIMand DMARC

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments