Outlook emails not deliverable to yahoo and aol

Just to reiterate for you and all the people coming here, thinking Microsoft can fix this for you, they cannot. If you are using your own domain (aka: custom domain) for email hosted in M365, you need to work with your IT or your domain host, or do your own research to confirm that the necessary DNS records.

I find SPF records are the easiest to create and manage. You can look up your SPF record by doing a google search for "spf lookup". I most often use the checker from MX Toolbox. If you are using M365, your SPF should look something like this -

v=spf1 include:spf.protection.outlook.com ~all

At the bottom of the lookup, it will tell you "Reported by", this will tell you who is hosting your DNS, that is where the SPF record gets created / modified. You log in or reach out to that DNS hosting company, and create or edit the TXT DNS record for SPF there. Setting up DKIM and DMARC gets a little more complicated, and are not necessary if you have a valid SPF record, and turn off the SPF record for the "OnMicrosoft.com" domain which I outlined in my post on page 2 of this thread.

FOR ANYONE continuing to post to this thread looking for a solution, they only way the community can offer insight into your specific problem will be for you to post your domain name, then we can lookup the details and try to offer additional guidance.

It is a custom domain, but I'm not sure I'm comfortable saying my domain name (I'm sure I'm being paranoid). I will say that it is hosted by Microsoft365 and the domain was purchased through a 3rd party vendor (Nelnet, if it matters).

Look up your SPF record by doing the Google Search for SPF Lookup and post back what it returns. If it has your domain in there, just replace it with mydomain.com instead of the actual domain name.

Also if you share the "Reported By" that will confirm to us which company is hosting your DNS, it could be your domain registrar, but it could also be someone else.

-Brad

It's not paranoia. I completely understand if you aren't comfortable with it. If you use custom domain, your IT is responsible for the fix. I did mention it on my previous post. Microsoft, Yahoo/AOL/Gmail can not fix the problem. Basically the problem is this, major mail providers (Gmail, Yahoo etc) start enforcing new policy. If your email domain does not conform with their new policy, they are not going to accept your email until you fix it.

You can forward this article to your IT (if there is one): https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/email-authentication-spf-configure?view=o365-worldwide

Jennifer,

I was in the same boat. Office manager, not an IT person. I had to reach out to the help desk for the 3rd party vendor, they finally gave me the DKIM and DMARC records to add to the DNS records. My domain host added them in for me (that was another day in the chat room).

There were also 2 SPF records and you're only supposed to have one, as I understand. So the second one was deleted.

I would reach out to your 3rd party provider and your domain host. My email seems to be sending to all addresses now.

Good luck!

The domain for our emails is "@mcbc.org".