Amazon SES - DKIM
-
Hello,
I'm trying to set SES for my Cloudron, and I've encountered a problem with your documentation.
The docs mention "Go to Amazon SES dashboard and add a new domain to verify under Domains. Leave the Generate DKIM Settings unchecked since Cloudron has already generated DKIM keys".
There's no such option in SES.
The only two options are "Provide DKIM authentication token", and "DKIM signatures" (Which can either be enabled or disabled).
Using Cloudron's DKIM private key isn't possible, because then Amazon requires us to set a CNAME with a hostname (cloudron._domainkey. ) that is similar to the TXT field that Cloudron already sets, which isn't allowed.
So do your documents only refer to the signatures field?
Thanks in advance.
-
@locutus said in Amazon SES - DKIM:
Hello,
I'm trying to set SES for my Cloudron, and I've encountered a problem with your documentation.
Despite the outdated docs in this matter, the console have changed so I'm gonna guess you are using the new SES UI console, and it's supposed to be easier than before.
So, on SES Home you ahould see on the left bar a menu and the option "verified identities" simply go there and add a new one, click "Create identity" and choose "Domain" identity type.
Enter your domain name and click "create identity" that's it. No need to mess with the advanced dkim for now.
Following identity creation, Amazon SES will provide a set of DNS records that you will need to copy and paste in your DNS record for theis domain name.
Let us know the output you've got.
Andy
-
@micmc said in Amazon SES - DKIM:
Enter your domain name and click "create identity" that's it. No need to mess with the advanced dkim for now.
So that means I'll have to create the new DKIM DNS records regardless of the existing ones that Cloudron already created previously. Correct?
-
@locutus said in Amazon SES - DKIM:
@micmc said in Amazon SES - DKIM:
Enter your domain name and click "create identity" that's it. No need to mess with the advanced dkim for now.
So that means I'll have to create the new DKIM DNS records regardless of the existing ones that Cloudron already created previously. Correct?
Not exactly correct
I mean, if you already have "verified identity" domains then just make sure the DKIM DNS records on SES are the same registered at your DNS provider's record.If you have legacy TXT records they should still work if they're the same. However note that they have changed for CNAME records now and they should be changed to CNAME.
Andy