Recently, I have not been able to receive emails that are being forwarded. Cloudflare shows a DKIM failure; publicly, outside of Cloudflare, there are no failures. So I thought I would just delete or edit the DKIM, but it is locked and managed through Cloudflare. I should also note that this domain name has not had any changes and has been using the email forwarding for years with the current DKIM.
What steps have you taken to resolve the issue?
So I thought I would just delete or edit the DKIM, but it is locked and managed through Cloudflare. I should also note that this domain name has not had any changes and has been using the email forwarding for years with the current DKIM.
What are the steps to reproduce the issue?
sending an email to one of the forwarder addresses and it will not reach the the forwarding address. After that the only way to tell there is a failure is by viewing the Cloudflare email activity log.
I found out how to unlock and delete all the email records, but recreating the records did not fix the issue. No forwarding happens, and no failed to deliver notices appear anywhere except in the Cloudflare email activity log.
This domain name is irrelevant in this specific case.
No, the actual DKIM that is relevant for this case, is not managed through Cloudflare, and does not have anything to do with Cloudflare at all.
The problematic domain name is “BTXCHANGE.COM”.
“BTXCHANGE.COM” does NOT use Cloudflare.
The email that is failing DKIM, according to your screenshot, was sent from “BTXCHANGE.COM”, and apparently through Microsoft Office 365.
“BTXCHANGE.COM” has not been configured properly, with the appropriate DKIM records for their set up, with Microsoft Office 365.
Typically, you will need to add a couple of “_domainkey” entries, such as e.g. “selector1._domainkey” and "selector2._domainkey, which will be pointing towards a sub-domain on one of Microsoft’s own domain names, so that they can handle the DKIM publication for you, for the messages that you’re sending through their platform.
None of these DNS records exist on the name servers for “BTXCHANGE.COM”, which is name servers that are operated by QUIC.cloud.
That makes sense.
Adjusting DNS records in the zone file for “BTXSUPPORT.COM” will never be making any difference, when the problem is with the set up of the “BTXCHANGE.COM” domain name.
It doesn’t matter what email host you use to send to any @btxsupport.com; they all get that message now. If you send an email from Gmail, the false record is seen in the Cloudflare activity log, and no delivery occurs from Cloudflare to any domain name. Zero forwarding for the last day has occurred. It also didn’t matter if I changed the forward address to another email; same result.
