Reputation: 11
ProtonMail has rolled out support for receiving mail from custom domains, and I'm adding the necessary records to my project's Cloud DNS settings from within Google Cloud Platform. I added the MX and SPF records, and they checked out, but when I try to add the DKIM records I get a "Not Properly Set" error from ProtonMail's end. I followed the same format, putting protonmail._domainkey
in the hostname, adding it as a TXT
record, and including v=DKIM1; k=rsa; p=...
in the record value.
ProtonMail technical support wasn't very helpful, replying with a "we don't see your TXT DKIM records, please ensure they are being properly propagated" response.
I can provide the other records I've set if anyone thinks it would be helpful.
Upvotes: 0
Views: 1557
Reputation: 1
Are you able to retrieve your DKIM record with this tool: http://mxtoolbox.com/dkim.aspx
Enclosing your DKIM TXT entry in quotes may solve the issue. Many DKIM libraries have issues with spaces after the semicolons.
Did you attempt to use a key larger than 1024 bits?
If you provide the domain name that your are having an issue with, I will look at the DKIM information in the zone.
Upvotes: 0
Reputation: 1
Your DKIM record may need to be wrapped in quotes.
Try:
"v=DKIM1; k=rsa; p=..."
I had the exact same issue with DKIM on protonmail. Protonmail support suggested verifying the records via mxtoolbox.com. Since I could see that my TXT record wasn't showing up as I had written it, I emailed my domain provider for help. They added quotes to the TXT record, and then I could see the record properly on mxtoolbox.com.
Upvotes: 0