- Newest
- Most votes
- Most comments
The email you received is indeed relevant and important, even if everything appears to be working fine in your dashboard. This message indicates that there's an issue with your DKIM (DomainKeys Identified Mail) configuration, which is crucial for email authentication and deliverability.
Amazon SES periodically checks for the presence of the required DNS records for DKIM. If these records are not found, it can lead to the situation you're experiencing. There are a few possible reasons for this discrepancy:
-
DNS propagation: Changes to DNS records can take up to 72 hours to propagate fully across the internet. If you recently made changes, it's possible that Amazon SES hasn't detected them yet.
-
Incorrect record configuration: Even if the records are visible in your domain provider dashboard and MX TOOLBOX, they might not be exactly as Amazon SES expects them. Double-check that the CNAME records (for Easy DKIM) or TXT records (for BYODKIM) are correctly formatted and in the right location.
-
Regional differences: If you're using Amazon SES in multiple regions, ensure that DKIM is configured correctly for each region. The issue might be specific to the US East region.
-
Temporary DNS resolution issues: Sometimes, DNS servers can have temporary problems that prevent Amazon SES from verifying the records.
To address this:
- Verify that the DKIM records are correct and in the right place in your DNS settings.
- If you're sure the records are correct, wait for a day or two to see if the issue resolves itself as DNS changes propagate.
- If the problem persists, contact AWS Support for further assistance.
Even though everything seems to be working fine now, ignoring this warning could lead to DKIM signing being disabled for your domain in 5 days. This could negatively impact your email deliverability. It's best to address this issue promptly to ensure your emails continue to be properly authenticated and delivered.
Sources
DKIM issue not sure if relevant | AWS re:Post
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service
Relevant content
- asked 3 years ago
- asked 7 months ago
AWS OFFICIALUpdated 10 months ago- AWS OFFICIALUpdated 12 days ago
It could be a sign that your DNS provider is not reliably making the necessary DNS records available on the internet. Those records need to be accessible to all receiving mail servers, so that the public key for the DKIM signature can be queried during message delivery.