Urgent: SES DKIM Issue

I understand your frustration with the DKIM key rotation issue in Amazon SES. This situation where old DKIM keys continue to be used despite adding new ones and verifying them is concerning, especially with your urgent timeline.

Here are some potential causes and solutions to consider:

1. DNS Propagation Delay: Although your new DKIM records show as verified in the SES console, there might still be propagation delays across DNS servers globally. While verification typically completes within 72 hours, in some cases, it can take longer for the changes to be fully effective.

2. Multiple AWS Regions: If you're using Amazon SES in multiple AWS regions, you need to configure DKIM separately for each region. Check if you need to update DKIM settings in all regions where you're sending emails.

3. Email Sending Configuration: Ensure that DKIM signing is enabled for the specific identities (domains or email addresses) you're using to send emails.

4. Verification Status: Even though the SES console shows DKIM as successful, external systems might be using different methods to verify the DKIM setup, which could explain why the old keys are still being used.

Since you've already contacted AWS Support and they've escalated your case to the appropriate team, continue following up with them as they have direct access to your account configuration and can provide specific guidance. In the meantime, you could try:

• Verifying your DKIM records using external DNS lookup tools to ensure they're publicly visible
• Double-checking that the DKIM CNAME records in your DNS settings exactly match what Amazon SES provided
• If possible, sending a test email and examining the headers to see which DKIM keys are being used

If the issue persists and you don't hear back from AWS Support in time, consider temporarily using an alternative email sending solution for your urgent needs while this issue gets resolved.
Sources
DKIM not propagating after more than 5 days | AWS re:Post
DKIM Verification Stuck in "Pending" for domain | AWS re:Post
DKIM-verification issues | AWS re:Post