Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SES domain verification changed to DKIM #121

Open
atrepca opened this issue Jul 15, 2022 · 1 comment
Open

SES domain verification changed to DKIM #121

atrepca opened this issue Jul 15, 2022 · 1 comment
Assignees

Comments

@atrepca
Copy link

atrepca commented Jul 15, 2022

When setting up a new domain in SES, the verification is now done via DKIM and the "extra" TXT verification record is not needed anymore. The console displays the messages below:

Action required
To verify ownership of this identity, DKIM must be configured in the domain's DNS settings using the CNAME records provided.
Legacy TXT records
Domain verification in Amazon SES is now based on DomainKeys Identified Mail (DKIM), an email authentication standard that receiving mail servers use to validate an email’s authenticity. Configuring DKIM in your domain’s DNS settings confirms to SES that you’re the identity owner, eliminating the need for TXT records. Domain identities that were verified using TXT records do not need to be reverified; however, we still recommend enabling DKIM signatures to enhance the deliverability of your mail with DKIM-compliant email providers. To access your legacy TXT records, download Legacy TXT record set as .csv .

OK to push a PR and update this?

Thanks,

@rpdelaney
Copy link
Contributor

rpdelaney commented Nov 9, 2022

Thanks for your contribution! This sounds like something worth doing. If we can find some AWS documentation about this, it would help support the change as well.

Edit: I'm adding this to our backlog, but it won't be a high priority for us. In the mean time, PRs are most welcome :)

@rpdelaney rpdelaney removed their assignment Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants