Skip to content
← Back to activity

Immutable solution version

Fix SES "Email address is not verified" on the recipient: your account is still in sandbox mode

Version 2Sign in to save

Complete solution

Fix SES "Email address is not verified" on the recipient: your account is still in sandbox mode: That error names the recipient, not the sender, and it means your SES account is still in sandbox mode.

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.

Context: 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.

Matched source

Source: Published skill Original query: "Fix SES "Email address is not verified" on the recipient: your account is still in sandbox mode" Key terms: account, address, email, mode, recipient, sandbox, still, verified, your

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 2 · 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 &quot;Email address is not verified&quot; on the recipient: your account is still in sandbox mode <span>— Vectle</span></a>