I am having issue that Yahoo emails are not reaching recipients.

Anonymous

I am having issue that Yahoo emails are not reaching recipients. I am getting an error message but after 24hrs not even straight after. It's only come to my attention because in follow up calls, they are telling me that the emails never arrived..

Please advise me how to sort it out as is very important I can reach those yahoo recipients.

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.

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

147 answers

Anonymous

2024-03-13T20:13:09+00:00

Thanks. That did the trick.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-03-13T19:15:00+00:00

Microsoft says it's not their issue. Yahoo is requiring additional security from senders to their service. Why and why all of a sudden is the question.

Implementing DKIM on the Microsoft side and adding the DNS records on the sender's domain DNS fixes the problem.
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-13T19:11:59+00:00

Microsoft has basically taken the corporate market. Most of my clients are on Microsoft's Exchange platform for email.

Mail from a private domain is sent through Microsoft. In order for most receiving mail servers to accept the email, an SPF record is required on the private domain's DNS. The receiving server checks to see if there's an SPF record that allows the sending server (in this case, Microsoft) to send the email on the private domain's behalf.

When setting up a Microsoft account, they provide all of the DNS records that need to be updated on the domain's DNS. Until recently (last Thursday), Yahoo is requiring more than the SPF record Microsoft provides - now they're requiring DKIM. It's just another slightly more complicated step to enable. It's just the sudden requirement from Yahoo that has everyone scurrying.

Oddly, from what I see, Yahoo is only requiring DKIM from Microsoft. I have other clients with a variety of mail servers that don't have a problem sending to Yahoo with only an SPF record.

Hope this makes sense.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Ron-6928 4,991 Reputation points

2024-03-13T18:36:48+00:00

That is correct. Create or edit those SPF, DMARC and DKIM records at turbify.com (based on your example).
Was this answer helpful?

0 comments No comments
Anonymous

2024-03-13T18:31:35+00:00

This has been happening since last Thursday. It's an issue with Yahoo receiving email from Microsoft. It's not something that you can do on your side. Anyone sending from Microsoft 365 to Yahoo needs to implement DKIM on their domain and Microsoft account. This requires that they turn on DKIM on their Microsoft account and add DKIM records to their domain's DNS.

You can try talking to Yahoo but they'll just blame Microsoft. Convincing your contractors that it's something they have to do might be difficult but it's currently the only way it will work - that is, until Microsoft and Yahoo work out their differences.

So to clarify, are you saying many private domains us MS365 to send email? For example, it's possible a domain like mypets.com, uses MS365 to send outbound emails to a Yahoo address? So if that domain has DNS hosted by someone like ns1.turbify.com then you'd need to add those records to that DNS server, correct?
Was this answer helpful?

0 comments No comments