1 Answer
- Newest
- Most votes
- Most comments
0
Hi, to troubleshoot Amazon SES email verification issues when using WorkMail:
- First, verify your DNS configurations are correct:
# Check MX record dig MX yourdomain.com # Expected output should include: # inbound-smtp.region.amazonaws.com # Check DKIM records dig +short TXT *._domainkey.yourdomain.com # Check SPF record dig +short TXT yourdomain.com
- Verify your domain in SES first:
aws ses verify-domain-identity --domain yourdomain.com
- Check required DNS records:
- TXT record for domain verification
- DKIM CNAME records (3 records)
- MX records for WorkMail
- Custom MAIL FROM domain records (if configured)
Example DNS records:
# Domain verification
_amazonses.yourdomain.com TXT "verification-token"
# DKIM records
token1._domainkey.yourdomain.com CNAME token1.dkim.amazonses.com
token2._domainkey.yourdomain.com CNAME token2.dkim.amazonses.com
token3._domainkey.yourdomain.com CNAME token3.dkim.amazonses.com
# MX record
yourdomain.com MX 10 inbound-smtp.region.amazonaws.com
# Custom MAIL FROM
mail.yourdomain.com MX 10 feedback-smtp.region.amazonaws.com
mail.yourdomain.com TXT "v=spf1 include:amazonses.com ~all"
- Troubleshooting steps:
- Check spam folder
- Verify WorkMail email rules
- Ensure WorkMail organization is in the same region as SES
- Check WorkMail console for delivery issues
- Review SES sending statistics
- If still not receiving verification email:
# Use AWS CLI to check identity status aws ses get-identity-verification-attributes \ --identities "yourdomain.com" "email@yourdomain.com" # Check if domain is out of SES sandbox aws ses get-account-sending-enabled # List all identities aws ses list-identities
For more information, see:
If issues persist:
- Try verifying a different email address temporarily
- Contact AWS Support
- Consider using AWS Support's SMTP test tool
Remember: DNS changes can take 24-48 hours to fully propagate.
answered 2 months ago
Relevant content
- AWS OFFICIALUpdated a month ago