SES production access
Get out of the SES sandbox so you can send to anyone.
A new SES account starts in the sandbox. It only delivers to verified identities, and it caps your volume. That includes the sign-in emails sesameSend sends to teammates: until you leave the sandbox, the sender and every recipient must be verified. setup-aws.mjs --verify <email> does that for each address.
Request access
In the AWS console, open SES in us-east-1, then Account dashboard, then Request production access. AWS asks for:
- The type of mail you send (transactional, marketing, or both).
- Your website URL.
- A description of your use case and how recipients sign up or opt in.
- How you handle bounces and complaints. sesameSend suppresses hard bounces and complaints automatically, and honors unsubscribes.
- Your expected sending volume.
Be specific. A one-line request is the usual reason for a rejection or a follow-up question.
The wait
AWS reviews the request by hand. Expect one to three days. It can be faster, and a request that needs more detail takes longer. You can keep working in the sandbox meanwhile, using verified addresses and the resend.dev simulator addresses.
After approval
- Raise
BROADCAST_SEND_RATE(emails per second, default 1, the sandbox limit) to your new SES quota. - Check your sending quota in the SES dashboard, and set
OPENSEND_MONTHLY_EMAIL_LIMIT(default 50000) to match. - Add your sending domain. See Domains and DKIM.