Forum Discussion
Can't Enable DKIM in Office 365
AOL, Yahoo, and Verizon (using the same email server) are now requiring that SPF, DKIM, and DMARC be enabled for emails sent to those addresses. I saw a report that Google will soon require this too...
You mentioned that DKIM was already enabled without CNAME resource records.
Activating requires two CNAME records in an external DNS zone of the M365 custom domain, not an internal DNS zone. EXO checks the availability of the correct CNAME records before activation of DKIM.
What do the mean by "4 accounts on 4 different providers"?
There should only be one name server provider for the DNS records of a custom domain.
May be I am getting this wrong.
-Thomas
ThomasStensitzki-MVP The DKIM being enabled on my own account could be a relic of a previous name server. I moved the domain and website. I do not remember enabling DKIM in the past. If I can straighten the other accounts out, I will revisit my own accounts.
There a actually 6 accounts in question. I "inherited" a couple of them. I moved 2 of the accounts because the previous provider did not support an upgrade to the version of MySQL that I needed. There are 2 accounts that I don't handle the website for, so I left them alone. 2 other accounts were at different providers when I took them over. There was no reason to disrupt them.
I have managed to get DKIM and DMARC working on 2 of the accounts, it may be a question of patience on my part.