SimonH8
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
Thank you matey 🙂
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
Thank you this is information that I didn't really know. DNS is not my strong point :D.
I'll pass this information over to Microsoft and ask them to investigate it on their side.
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
Okay I appericate that 🙂 thank you, I've replied to Microsoft I'll see what they said however the last time I spoke to them, They stated that they only provide the CNAME and then this is hosted within a DNS provider (CloudFlare) in mycase.
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
I've regenerated it hence why it isn't the same now. But it was the extact same
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
It was the same key which is why it making me believe its was from google.
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
Oh okay, I was under the impression that this is Google Workspace as I found this key within an old TXT record that was removed a while ago.
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
The selector1 etc is Microsoft.
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
Sorry,
I'm talking about the Public Key
"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwOGhW5w3vTC3j59hP9DeFARJRvcnzftb2bn/KNdwaUesVYIalDQXKrgi6BZZps6C/mX5Brc18JSPKuUvhuK4T//pZKX/OimvEuxHTtyTs2ij7b4CAZBvn4t8Ts+OLf2Fwx0UMd/Cm8slYHnwxnFWT9DKnXTjeLKRqHu3zxEuyE5kelzfx/kZJH/cLgFl0y48"
This key is Google Workspace rather than Microsoft
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
I think this issue has been an issue since we moved from Google Workspace to Microsoft and I've not noticed.
We removed the public key which came from Google Workspace over 5 months ago, so I'm not sure as to why this is caching. But we'll see what Microsoft say to the response.
Thank you again for assisting me
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
I've sent a reply over to them, stating this. However I'm under the impression they'll send it back to me.
Thank you for your answer :). Microsoft are trying to blame this on CloudFlare, however I don't see it within Cloudflare, hence the question to you lot 🙂
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
I appreicate that, but I'm just going off what I've been told by Microsoft
We have checked the last message header sample you gave and saw the error: DKIM=fail (body hash did not verify)", it means that the DomainKeys Identified Mail (DKIM) signature verification failed because the hash value of the email's body did not match the value stored in the DKIM signature. As previously mentioned, this would be the expected result as the DKIM records being detected and published is still the records that were from Google. The old cache records will need to be cleared out and this would be on your host provider. Unfortunately, Microsoft cannot clear these old records as we only provide the DNS records to be published.
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
See I was under this impression however,
This public key was orginally set in Google "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwOGhW5w3vTC3j59hP9DeFARJRvcnzftb2bn/KNdwaUesVYIalDQXKrgi6BZZps6C/mX5Brc18JSPKuUvhuK4T//pZKX/OimvEuxHTtyTs2ij7b4CAZBvn4t8Ts+OLf2Fwx0UMd/Cm8slYHnwxnFWT9DKnXTjeLKRqHu3zxEuyE5kelzfx/kZJH/cLgFl0y48"
Now I don't understand why this is showing up? I'm assuming this is the reason our dkim is failing here? As this doesn't exist?
44 replies
CDCloudflare Developers
•Created by SimonH8 on 2/25/2025 in #workers-help
DKIM - old txt rather than CNAME
This happens on mantrasystems.com and mantrasystems.co.uk it looks to be looking at an old DKIM rather than the new CNAME.
I have no idea how to resolve this however our outbound email address seem to be failing dkim as this key is not the correct one.
44 replies