SendForever help
Log in Get started

Help Start

Leaving the SES sandbox

A new Amazon SES account starts in the sandbox, where it only delivers to verified addresses, until AWS grants it production access. This page covers what works in the sandbox, how test emails reach you there, how to request production access from SendForever, and how the app tracks AWS's answer.

What the sandbox is

AWS reviews every Amazon SES account before it can email anyone. Until then, the account is in the sandbox, which:

  • Only delivers to verified addresses.
  • Sends up to 200 emails a day.

The sandbox applies to the whole account in its region, not to one domain. Anything that sends through the account, SendForever or your own app, can only reach verified addresses. AWS grants production access per region, and it does not carry over to other regions. That is why, when you connect an account that already sends, SendForever asks you to pick the region you send from (see Your AWS account).

What works in the sandbox

You can set up everything before AWS answers:

  • Connect your AWS account, add domains, publish their DNS records and have Amazon SES verify them.
  • Send yourself test emails, once Amazon SES has verified your address (see below).
  • Import audiences and write templates. See Audiences and Templates.

What waits for production access:

  • Campaigns. A campaign's checks fail while the account is in the sandbox, and the campaign can go out once AWS approves the request. See Campaigns.
  • Any email to an address that is not verified, including what your app sends.

Where the app shows the sandbox

  • The team's Overview lists it under Issues: "Your Amazon SES account is in the sandbox", "AWS is reviewing your request for production access" or "AWS declined production access". The row links to the AWS account page.
  • On the team's Settings, under AWS account, the Production access row shows Sandbox or Enabled, and a callout says where the request stands.
  • A domain's Settings shows the same callout. Each domain also lists Production access among the checks that need attention, in the domain lists and on the overview.
  • A campaign's checks say whether it can go out.

Test emails in the sandbox

The test email goes from your domain to the address you signed in with. You send it from Getting started, or with Send me a test email in the actions menu of a domain's Settings. The domain must be verified first.

In the sandbox, your own address has to be verified too:

  1. Click Send me a test email.
  2. If Amazon SES refuses your address because it is not verified, SendForever asks Amazon SES to verify it. The page then says that Amazon SES just emailed your address a link to verify it.
  3. Open the link in that email from Amazon SES.
  4. Click Send me a test email again.

The address stays verified in your Amazon SES account, so later tests reach it until the account leaves the sandbox. If you send again before you open the link, SendForever reminds you that the address is still waiting for verification. A link expires after a day. To get a new one, delete the address in the Amazon SES console and send the test again.

A domain sends up to 5 test emails an hour, and each request to Amazon SES to verify your address counts toward that limit. If the refusal names the sender instead of you, Amazon SES has not verified the domain. The message shows AWS's own words.

Request production access

Team owners and admins can request it in three places:

  • The last step of Getting started, Ask AWS to let you email anyone, which opens once your domain is verified.
  • The team's Settings, under AWS account: click Request production access in the sandbox callout.
  • A verified domain's Settings: click Request production access in the sandbox callout.

AWS approves requests faster once a domain is verified, so verify a domain before you ask.

The form asks for the same details as the Amazon SES console:

  1. What do you send? Choose Transactional (one email to one person, triggered by what they did: receipts, password resets, notifications), Marketing (one email to many people on a list: newsletters, announcements, promotions) or Both. AWS takes only one kind, so Both is sent as marketing, whose stricter review covers transactional email too. It is preset from your first domain's purpose.
  2. Website: where AWS can see who you are and what you send. It must be an https:// address. It is preset to your domain, or to its parent for a subdomain such as news.example.com.
  3. Tick I only email people who asked for it, and I handle bounces and complaints. Amazon SES asks every account to confirm this, and the request cannot be sent without it.
  4. Click Send request to AWS.

SendForever sends the request to Amazon SES in your account. It sets English as the contact language and adds your email address as a contact for the review. If AWS is already reviewing a request, made here or in the AWS console, SendForever counts the request as made. If AWS refuses the request, the form shows AWS's message.

Members cannot request production access, but they can see where the request stands.

How long AWS takes

AWS answers within 96 hours, by email. While it reviews the request, SendForever shows AWS is reviewing your request for production access: "Until then Amazon SES only delivers to verified addresses, up to 200 emails a day, so tests to yourself already go out."

Once you have sent the request, your part of Getting started is done.

How the app follows AWS's answer

SendForever does not poll AWS in the background. It reads your account's status from Amazon SES:

  • When you open the team's Overview or AWS account page while the account is in the sandbox, at most once a minute. A request made in the AWS console shows up this way too.
  • Whenever SendForever checks one of your domains, for example when you click Check again at the top of the domain's page.
  • When you open a campaign that has not been sent yet.

When AWS grants production access, the Production access row shows Enabled. The sandbox callouts and the Overview issue go away, and each domain's Production access check passes the next time the domain is checked. If AWS's email arrived but the app still shows the review, open the AWS account page.

If AWS declines

The app shows AWS declined production access: "AWS explains why in the AWS Support Center, where you can answer it. You can also send a new request."

  1. Open the AWS Support Center in your AWS account and read AWS's reply to the case.
  2. Answer it there, or fix what AWS asked about.
  3. To send a new request from SendForever, click Request again on the AWS account page, on a verified domain's Settings, or on the last step of Getting started.

While a request is declined, the overview shows owners and admins Finish getting started again, with "AWS declined production access. You can answer it, or send a new request."

Common questions

How long does AWS take to answer?

Within 96 hours. AWS answers by email, and SendForever shows the answer once it reads your account again.

AWS approved my request, but SendForever still says it is reviewing. Why?

SendForever reads AWS's answer when you open a page that needs it, not in the background. Open the team's Overview, or Settings, then AWS account. While the account is in the sandbox, these pages read your account when they open.

Can I send email while I wait?

Only to verified addresses, up to 200 emails a day. Test emails to yourself work once Amazon SES has verified your address. Campaigns wait for production access.

Your account is in the sandbox and your address is not verified yet. Open the link in the email from Amazon SES, then click Send me a test email again.

A link expires after a day. Delete your address from the identities in the Amazon SES console, then send the test again. Amazon SES emails you a new link.

Do I need a verified domain before I request production access?

No, but AWS approves requests faster once a domain is verified. Getting started asks for production access only after that, and a domain's settings offer the request once that domain is verified. The AWS account page lets you request it at any time.

Who can request production access?

Team owners and admins. Members see where the request stands but cannot send it.

AWS declined my request. What now?

Read AWS's reason in the AWS Support Center and answer it there. You can also send a new request with Request again.

I already have production access in another region. Why is SendForever in the sandbox?

Production access does not carry over to other regions. SendForever uses the region your team connected in. To use the region where you have production access, the team has to connect again in that region. See Your AWS account.

Can I request production access in the AWS console instead?

Yes. SendForever reads your account's status from Amazon SES, so a request made in the console shows up here the next time SendForever reads the account, for example when a domain is checked. If you send a request from SendForever while AWS is still reviewing the one from the console, SendForever counts it as made.

Still stuck?

, which answers from these pages.

No page or section has those words.

Ask AI

ChatGPT or Claude answers in a new tab, from the SendForever docs. Only your question goes with it, nothing about your team.

Or read the help center

ChatGPT Claude