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: Newest
  1. 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
  2. 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
  3. Anonymous
    2024-01-26T11:49:51+00:00

    DO NOT, AND I MEAN DO NOT FOLLOW ANYONES SUGGESTIONS OR FIXES ON HERE!!!!!!

    Assuming it was a simple fix I have now messed up my DNS records on 365 because of others assuming their fix is going to fix others.

    Be mindful and ask your host first if changing anything or it could mess your DNS records if you are not using Microsoft's.

    Also make sure you are not using a CDN (Check you web developer/host) again to see if this will also have a knock on effect.

    I am happy for those that have fixed it for them but not everything is setup the same. I have learned the hard way. If anything Microsoft should be sharing a page on how to fix this with different setup i.e. Host/ CDN and Microsoft DNS options.

    Be extra careful. I did this on a bad day knowing I will be working over the weekend now to resolve an issue Microsoft seem to struggle with, or at least be aware of and resolve as this issue has now been going on since 2013 and has come back early this year again.

    Complete mess and can bring a website down to its knees if you have custom DNS setups.

    Was this answer helpful?

    0 comments No comments
  4. Ron-6928 4,991 Reputation points
    2024-01-25T19:09:58+00:00

    >> I am assuming this issue is still not resolved.

    >> I wondered if this was a DNS thing.

    It won't be resolved until the user (or their IT personnel) fixes it.

    It most likely is. Do you have proper mail related DNS records (SPF, DMARC etc)?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-01-25T18:43:23+00:00

    I am assuming this issue is still not resolved. I am getting the same message when I send emails from my business email to my personal sky email address and also to a friends yahoo email.

    I have tried making my business email a 'safe sender' on my sky email but its still not working. However, this mainly seems to be impacting the calendar invitations as some emails are getting through to recipients.

    please let me know if there is anything I need to do in the sky email set up to stop this from happening. I wondered if this was a DNS thing.

    Here is the message :

    Your message couldn't be delivered. Despite repeated attempts to contact the recipient's email system it didn't respond.

    Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that their email system isn't accepting connection requests from your email system. Give them the error details shown below. It's likely that the recipient's email admin is the only one who can fix this problem.

    For more information and tips to fix this issue see this article: https://go.microsoft.com/fwlink/?LinkId=389361.

    Was this answer helpful?

    0 comments No comments