- Newest
- Most votes
- Most comments
Seems you are dealing with a DKIM alignment issue where Amazon SES is signing emails with its own domain (d=amazonses.com) instead of your custom domain. Please consider on below:
Verify DKIM Configuration:
-
Ensure that DKIM is enabled for your custom domain in the Amazon SES console. Navigate to the domain identity settings and confirm that DKIM is active.
-
Double-check the DNS records for your custom domain. Amazon SES requires specific CNAME records for DKIM verification. Make sure these records are correctly configured and propagated.
Mail From Domain Configuration:
- Amazon SES uses the MAIL FROM domain for SPF and DMARC alignment. Ensure that the MAIL FROM domain matches your custom domain and is correctly configured in SES.
DMARC Policy:
- Check your DMARC policy settings. If your DMARC policy is set to "strict," it requires an exact match between the FROM header domain and the DKIM signature domain. Consider switching to "relaxed" alignment if strict alignment is causing issues.
Troubleshooting Tools:
- Use tools like dig or nslookup to verify that the DKIM CNAME records are correctly set up and publicly accessible.
Amazon SES will sign with d=amazonses.com whenever the identity that sent the email is verified only as an email address or when custom DKIM signing for the verified domain is not activated. For domain alignment under DMARC, SES must DKIM‑sign with your own domain—for example, d=subdomain.mydomain.com—which happens only after you enable Easy DKIM or upload your own DKIM keys for that domain identity. In the SES console, open Verified identities, select your sending domain (not just the email address), choose DKIM, and confirm that “Easy DKIM” is enabled and shows three CNAME records published in Route 53 (or your DNS).
—Taz
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
