This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 76%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Hi,
So I am using Office 365 as my email host along with GoDaddy as my domain host. I already setup the email and using it but all my emails keep going to spam due to lacking a DKIM header.
I already pass all SPF and DMARC checks. And for the DKIM, I added the CNAME tags including the suggested selectors by microsoft on Godaddy and activated the DKIM signing on Microsoft.
Online tools confirm that these tags are now public. Even the Microsoft DKIM self check tool says my DKIM is configured correctly. MXtoolbox says my DKIM record is found and valid and that the public key is present.
However until now all my outgoing emails are missing the dkim headers saying: dkim=none (message not signed).
DKIM signing is enabled on my custom domain since the second of October. I figured by now it should be working. Any idea what can be done next to fix this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 31%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJX%3C/text%3E%3C/svg%3E)
Hello, I'm here to confirm that is there any progress in your question?
Hi,
Not really. I opened a support ticket and I'm still awaiting an answer from Microsoft. Hopefully this gets resolved soon.
Hi, I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
So the issue is now resolved. Microsoft confirmed that this was an issue on their backend. Have no idea what was done to fix it though.
Hi @Amr Abdelsabour ,
Glad to know the issue is solved and you could accept Andy's reply as the answer to close the thread!
If everything looks correct on the 365 server side, I would open a ticket with support if you arent seeing anything in the headers of the messages.
One thing you could try is to rotate the DKIM sigs and see if that pops it.
Since its not working anyway, it wont hurt:
https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/use-dkim-to-validate-outbound-email?view=o365-worldwide#steps-to-manually-upgrade-your-1024-bit-keys-to-2048-bit-dkim-encryption-keys
Just tried it. I am assuming it takes a while to be able to verify if it works after rotating the keys. So let's see if it works in the next 2-4 days. (I tried it now after rotation but unfortunately it didn't work).