Outlook emails not deliverable to yahoo and aol

Brad, when I click on Settings, it redirects me to www.domainspricedright.com and wants me to sign in. This is who provides my domain but they do not manage my DNS settings. Anyway, I can't seem to get into the Admin Center and go any further than Settings.

Can you explain or do you know why this all of a sudden acted up again? Once I got it fixed in late January, it's been working perfectly until this last Friday.

Laura

I have the same story. We added a txt record as recommended by godaddy to DNS. This fixed the issue since January of 2024. It just returned yesterday.

domain.example is missing an SPF record, which may prevent you from sending email. You need to add v=spf1 include:secureserver.net -all as a TXT record to your DNS.

Why would you tell people whose email is hosted by Microsoft to add a GoDaddy SPF record? This is incorrect advice. This thread is for people who have this issue with domains hosted on Microsoft 365.

-Brad

Brad,

I wrote earlier and deleted the "bad advice" SPF record. However, it is my understanding that iPage, my web site provider, is GoDaddy. My domain provider does not manage my DNS settings, iPage does. So, maybe the prior advice was correct for me?

Also, I've looked high-and-low, in the past and again now, for the  *.onmicrosoft.com domain in the Microsoft 365 admin center and I can't find it! And I've tried, again, to read Ron's article but it is totally Greek to me. I'm so lost!!!!!! I just cannot figure out how to do the DMARC setting.

Laura,

SPF is for email flow, it does not matter who hosts your DNS, that does not affect the record. If only matters who hosts your email. So if my DNS is with iPage, or GoDaddy, or Network Solutions, or CloudFlare, regardless, the SPF record will be the same.

I have never run into someone on M365 that does not have the OnMicrosoft.com domain.

If you log in to admin.microsoft.com, then click on "Show all" on the left, then under "Settings", click on "Domain", do you see your OnMicrosoft doamin there?

-Brad

Brad, thank you for your input. I've deleted the incorrect SPF record.

The DMARC has me stumped though, because I thought that I copied it directly from Ron. I'll go back and look. I've deleted it for now.

I guess I should wait to see if removing the DMARC record fixed it, but I'll take note of Ron's comments on page 7.

The incorrect SPF record was just added yesterday(?), so there is something else that has caused this to happen again. I've been error-free for over a month now, until just a couple of days ago.

iPage controls my DNS settings but they have no clue how to help me. I've had to do this on my own.

Laura

Hmmmm. Now I'm wondering if your invalid SPF caused your DMARC to fail, and maybe it was good before. Don't re-create it until you have an issue again though, might as well see where we are first.

-Brad

I have the same story. We added a txt record as recommended by godaddy to DNS. This fixed the issue since January of 2024. It just returned yesterday.

domain.example is missing an SPF record, which may prevent you from sending email. You need to add v=spf1 include:secureserver.net -all as a TXT record to your DNS.

Why would you tell people whose email is hosted by Microsoft to add a GoDaddy SPF record? This is incorrect advice. This thread is for people who have this issue with domains hosted on Microsoft 365.

-Brad

Brad,

I wrote earlier and deleted the "bad advice" SPF record. However, it is my understanding that iPage, my web site provider, is GoDaddy. My domain provider does not manage my DNS settings, iPage does. So, maybe the prior advice was correct for me?

Also, I've looked high-and-low, in the past and again now, for the  *.onmicrosoft.com domain in the Microsoft 365 admin center and I can't find it! And I've tried, again, to read Ron's article but it is totally Greek to me. I'm so lost!!!!!! I just cannot figure out how to do the DMARC setting.

Thanks Brad. How do I get of this tread?

At the top of this page, there is a "subscribe" button you can click and unsubscribe.