Solution skill
Fix SES "Email address is not verified" on the recipient: your account is still in sandbox mode
Complete solution
Shows how to fix sES "Email address is not verified" on the recipient: your account is still in sandbox mode. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
That error names the recipient, not the sender, and it means your SES account is still in sandbox mode. In sandbox you can only send from verified identities AND to verified identities.
Steps
- That error names the recipient, not the sender, and it means your SES account is still in sandbox mode. In sandbox you can only send from verified identities AND to verified identities. To send to real users you have to request production access: open the SES console, go to Account dashboard, and request production access (or open an AWS Support case for an SES sending-limit increase). Once AWS moves the account out of sandbox, the same verified sender can mail any recipient. If you only ever need test traffic, verify the recipient address too and it will go through while you wait.
When to use
You are seeing this: That error names the recipient, not the sender, and it means your SES account is still in sandbox mode. Use this skill when you run into "Fix SES "Email address is not verified" on the recipient: your account is still in sandbox mode".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Stack Overflow #37528301 (accepted answer, 555 votes): The reporter verified both their domain and their sender address in SES, yet sending a test email from the console failed with "Email address is not verified" naming the recipient address, not the sender. They were sending from a verified identity to an outside mailbox and could not figure out what was unverified.
Verified resolution: That error names the recipient, not the sender, and it means your SES account is still in sandbox mode. In sandbox you can only send from verified identities AND to verified identities. To send to real users you have to request production access: open the SES console, go to Account dashboard, and request production access (or open an AWS Support case for an SES sending-limit increase). Once AWS moves the account out of sandbox, the same verified sender can mail any recipient. If you only ever need test traffic, verify the recipient address too and it will go through while you wait.
Source URL: https://stackoverflow.com/questions/37528301
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_6sBP5BmJ_o-XJAEI-AIBcA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Fix SES "Email address is not verified" on the recipient: your account is still in sandbox mode <span>— Vectle</span></a>