Forum Discussion
New tenant and domain classed as phishing
Hi everyone.
I have searched and tried to find an answer on my questions but can't find anything.
I configured a new tenant with a new custom domain with "Enabled Security Defaults".
When my ...
It appears that you have already published the SPF record.
However, I was unable to find CNAMEs required for DKIM.
You can follow https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/use-dkim-to-validate-outbound-email?view=o365-worldwide to configure DKIM.
After that you can configure DMARC as well by following https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/use-dmarc-to-validate-email?view=o365-worldwide
SPF, DKIM, and DMARC will help in deliverability of the emails.
However, I was unable to find CNAMEs required for DKIM.
You can follow https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/use-dkim-to-validate-outbound-email?view=o365-worldwide to configure DKIM.
After that you can configure DMARC as well by following https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/use-dmarc-to-validate-email?view=o365-worldwide
SPF, DKIM, and DMARC will help in deliverability of the emails.
I deleted records because I thought they were the ones causing the problem.
But I will add them again and see if I can activate DKIM.
The problem with DKIM is that M365 can't "create" encryption key.
BR
Thomas M
- Based on my experience, yes, the DNS records are needed to successfully configure DKIM.
I was after long time waiting able to activate DKIM and Dmarc.
So I hope this might resolve my problem, if not I will contact Microsoft about it.
Thanks for the help and I wish you Marry Christmas and happy new year.
BR
Thomas M
- You too have a Merry Christmas and Happy New Year.
If the problem persists, check content and signature in the emails.
If the signature has hyperlinks, you may get a higher SCL score. Try removing the signature and see if it helps.
