Help for owners
My emails through Amazon SES are not reaching customers
Short answer
New Amazon SES accounts start in a sandbox, separately in each Region. There you can only send to verified addresses, up to 200 messages per 24 hours and 1 per second. To send to customers you must request production access and explain your sending. AWS documents 96 hours for its initial reply.
Does this sound like your situation?
- Password reset and order emails work for me but not for customers.
- My app logs say the address is not verified.
- Email worked in one AWS Region and not in another.
- I applied for production access and the answer was no or asks for more detail.
- A limit of 200 emails a day stopped a launch.
Why does this happen?
The account is still in the sandbox
AWS places all new SES accounts in the sandbox. In it you can only send to verified email addresses and domains, or to the mailbox simulator, at most 200 messages per 24 hours and 1 message per second.
Confirmed by docs.aws.amazon.com
Sandbox status is per Region
The sandbox status is unique to each AWS Region. Getting out in one Region does not change another, so an app that sends from a different Region than you requested stays stuck.
Confirmed by docs.aws.amazon.com
The request was not filled in clearly
The request asks whether your mail is marketing or transactional, your website URL, contacts and an acknowledgement that you send only to people who asked for email and handle bounces and complaints. A vague website or description makes a decision harder.
Confirmed by docs.aws.amazon.com
Sender identities are not verified
Even in production you must verify the From, Source, Sender and Return-Path addresses you use. A domain left unverified is a common reason sends fail.
Confirmed by docs.aws.amazon.com
Sending from a server hits port 25 throttling
AWS notes that sending SES mail from an EC2 instance may also need the throttle on port 25 removed. Using a different method avoids that.
Confirmed by docs.aws.amazon.com
What can I do about it today?
- Open the SES account dashboard in the right RegionCheck which Region your app sends from. Then look for the banner saying the account is in the sandbox.
- Verify your sending domain firstAWS says verifying a domain before requesting production access helps a request get approved faster. Ask your developer to do the domain records.
- Prepare an honest descriptionWrite who your customers are, how they sign up, what emails you send, how you handle bounces and how people unsubscribe. Do not buy or import lists.
- Submit the request once, carefullyAWS says you cannot edit the details until the review is complete. Check the website URL and contact addresses before you submit.
- Keep a manual fallback for urgent mailFor launches, tell customers by another route while you wait.
- If refused, do not resubmit the same textRead the reply. Fix what it names, then answer through the support case.
When should I bring someone in?
- The request was declined and you do not understand why.
- Mail goes out but lands in spam or bounces.
- You plan to send campaigns to an existing list.
How do I handle it?
- Verify the domain and sender recordsDNS records for identity and signing are set up and checked before anything is requested.
- Describe the real sendingI help write a plain description: purpose, signup flow, expected volume, bounce and complaint handling.
- Wire bounce and complaint handlingBounces and complaints are recorded and the addresses are stopped, so the account stays in good standing.
- Test in the right RegionI confirm the app uses the Region that was approved and send test messages to inboxes I do not control.
- Plan for a refusalIf AWS says no, the reply is read together with you and either fix the cause or use a different sending service. I will say which fits.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
How long does AWS take?
AWS documents 96 hours as the period for its support team's initial response, and a grant may take longer if it needs more information. I cannot speed it up.
Can I raise the sandbox limit instead?
The sandbox limits are fixed at 200 per 24 hours and 1 per second. The route is the production request.
Do customers need to be verified in production?
No. AWS says in production you can send to any recipient, but you still verify the sender identities.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.