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-02-19T00:33:16+00:00

    The problem is almost certainly in the DNS configuration of their personal domains.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-02-19T00:24:57+00:00

    I use a yahoo account and this just started over the last 3 weeks. It was never an issue. However, both of the people emailing me are using personal domains and the emails are bouncing back to them saying I have the Microsoft issue.

    Was this answer helpful?

    0 comments No comments
  3. Ron-6928 4,991 Reputation points
    2024-02-15T15:39:46+00:00

    If you use custom domain and your mail related DNS records are either missing or incorrect, you will have the same problem. It will never go away unless you fix the problem yourself.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-15T14:04:03+00:00

    I am having the same thing and don’t use Microsoft 365

    Was this answer helpful?

    0 comments No comments
  5. Ron-6928 4,991 Reputation points
    2024-01-26T17:57:39+00:00

    There are 2 issues that I know at this time:

    1. Missing or incorrect DNS records (SPF, DMARC, DKIM) for customers who use their own domain name
    2. IP reputation (DNSBL)

    You are responsible for #1. Microsoft can't fix the problem for you.

    #2 (Microsoft IP addresses blacklisted on many DNSBL database) is Microsoft's responsibility.

    Was this answer helpful?

    0 comments No comments