You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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,
The text was updated successfully, but these errors were encountered:
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 :)
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:
OK to push a PR and update this?
Thanks,
The text was updated successfully, but these errors were encountered: