SES MessageRejected: Email address is not verified. The following identities failed the check in region
SES refused to send because the From address/domain isn’t verified — or the account is still in the SES sandbox, where recipients must be verified too.
Seen on:
AWS
Meaning
SES requires verified identities per region. In sandbox mode you can only send to verified addresses, which surprises people the first time a real user signs up.
Common causes
- From address/domain not verified in this region
- Account in SES sandbox and recipient not verified
- Using a different region than where the identity was verified
⚡ Quick fix
- Verify the domain (DKIM) in the sending region
- Request production access to leave the sandbox
- Configure the SDK with the SES region you verified in
Detailed fix by platform
AWS CLI
- bash
aws sesv2 get-account --region eu-west-1 --query ProductionAccessEnabled aws sesv2 create-email-identity --email-identity example.com --region eu-west-1
How to diagnose
- Identity — Verified in this region?
- Sandbox — ProductionAccessEnabled?
- Recipient — Verified (sandbox)?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in AWS
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026