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

That does not resolve the issue - contact evey yahoo email account that is emailed and then have them go and change their settings. Then email them again hoping they went and fixed the issue, all in the nick of business time. I dont think this will work. We need something on our end to swith for us to reach to yahoo emails. Or is this the road block to emails?

Thanks for the link, Ron. Apologies if my question a bit misleading.

That's an Exchange management question. Post it here: https://learn.microsoft.com/en-us/answers/tags/342/office-exchange-server-management

Hi everyone,

So yes, I have been having this issue for quite some time now, the issue I have that our email server's DKIM and SPF configuration are a bit incorrect you might say.

So, for starters, I've changed the SPF key on my external DNS, which is quite straight forward.

For my DKIM key, it's a bit tricky since our Exchange Server (Exchange Server 2016) doesn't have support native DKIM signature, so I download the 3rd party signer here: https://github.com/Pro/dkim-exchange/wiki and I changed the public key for the DKIM signer on our Exchange server and external DNS server.

After the troubleshoot, testing out our email to https://www.mail-tester.com/ and MxToolbox, giving result that our SPF and DKIM are up to date. That's okay but I still can't send email to a Yahoo user.

After further checking, we noticed that our PTR records in the original messages (we only checked Gmail) has a bit of difference before and after the issue, our email scanner server cannot be translated to it's public DNS address. Anyone can suggest why this is happening and what I can do to mitigate this issue?

Forget about non admins, I'm a mail admin and your post is still a bit confusing to me but I understand the big picture. No offense but I highly doubt non mail admin can understand the post.

>> They have done things to my domain DNS record that have been ineffective and/or that I learned subsequently breaks DNS - eg entering multiple SPF records. I have escalated to management on 2 occasions but been told it will go away by itself, or been told its a google problem.

The problem is editing a DNS record actually adds a new entry but it does not delete the old entry. That's how you end up with 2 SPF records. Edit normally adds a new one and automatically deletes the old one. Many GoDaddy customers have multiple SPF records problem. It makes it invalid and resulting in their email getting rejected.

>> Why this wasn't done when Microsoft 365 on GoDaddy was set up, I don't know.

I don't know how you get your mail hosting service, I did everything myself. That includes setting up SPF, DMARC and DKIM records correctly since the beginning of my subscription. I suspect GoDaddy didn't take care of it because it wasn't mandatory in the past or they expect customers do that on their own.

Most users who experience this problem are just mail users. They post problem here and wait/expect someone will fix it someday. They don't realize they are the only ones who can fix the problem.

I have been following a few similar discussion threads. I have told them the problem and what needs to be fixed. Occasionally I check back to see if they fix their DNS records. Nope. They're still missing or have invalid records. That tells me they don't understand my replies.