SendForever help
Log in Get started

Help Start

Getting started

Create a SendForever account and go through the Getting started page, from connecting your AWS account to asking AWS to let you email anyone. This page covers each of the six steps, what you can do while you wait for AWS or your DNS, and how to come back to the steps later.

Create your account

Sign up with your email address

  1. On the sign-up page, enter your Name, Email address and Password, then click Create account.
  2. SendForever emails you a 6-digit code, with the subject "Confirm your email address". The code expires after 30 minutes.
  3. On the Confirm your email page, enter the code in Confirmation code and click Create account.

Your account exists only after you confirm the code, so your email address is verified from the start. Each new account comes with its own team, named after you, and you own it.

On the confirmation page you can also:

  • Click Resend code for a new code. You can ask for one once a minute.
  • Click Use a different email to go back to the form.

After five wrong codes, the registration ends. Start again from the form to get a new code. After 20 wrong codes for the same address in a day, try again the next day.

A password needs at least 12 characters, with uppercase and lowercase letters, numbers and symbols. It must not appear in a known data breach.

Continue with Google

The sign-up and log-in pages offer Continue with Google. Google must have verified the address of your Google account.

  • If an account with that address already exists, you are signed in and the account is linked to Google from then on.
  • If not, SendForever creates an account, already verified, with its own team. The account has no password you know. To add one, use Forgot password? on the log-in page.
  • Google never replaces two-factor authentication. If your account has it on, you still enter your code after Google.

Joining from a team invitation

If someone invited you to their team, open the link in the invitation email. The form fills in the address the invitation was sent to, and only that address can use it. You join that team and start on its overview. You also get a team of your own. If you already have an account, the link takes you to log in instead. See Teams.

The Getting started page

The first time you open a new team as its owner or admin, SendForever opens Getting started: "About 10 minutes of your time. AWS's checks finish on their own." It is a separate page, without the app's navigation. The profile menu still lets you switch the theme, log out or delete your account.

A bar at the top shows the six steps:

  1. AWS account
  2. Choose plan
  3. Add domain
  4. DNS records
  5. Test email
  6. Send to anyone

Each segment is green when the step is done, amber while AWS or your DNS works on it, red when it needs your attention, and gray for steps you have not reached yet. Click a step you already reached to open it again. A finished step shows its result and a Continue button to the next one.

Only team owners and admins see Getting started. Members are taken to the team's overview, which tells them to ask an owner or admin when something is missing.

Step 1: Connect your AWS account

SendForever sends with Amazon SES from your own AWS account, through a CloudFormation stack you create there. The step walks you through it:

  1. Say whether you already send email with Amazon SES. Choose Not yet and SendForever sets up Amazon SES in the region nearest you. Choose Yes and pick the region you send from, because production access does not carry over to other regions. Choose No AWS account yet to get Create an AWS account: AWS asks for a card and a phone number, and a new account can take up to a day to be ready.
  2. Check who updates the stack. New features sometimes need a new version of the stack. SendForever comes chosen: SendForever applies each version when you ask, within limits the stack sets. Choose By hand in AWS to give SendForever no permission to change the stack. SendForever then shows you the steps to apply each version yourself. The stack keeps your choice, so to change it later you do it in AWS, with the steps under Stack updates on the AWS account page.
  3. Click Connect with AWS. CloudFormation opens with everything filled in. If AWS asks you to sign in, use the AWS account you want to connect, as the root user or an administrator.
  4. Create the stack. At the bottom, tick "I acknowledge that AWS CloudFormation might create IAM resources with custom names" and choose "Create stack". AWS takes a few minutes to create it.
  5. Come back here. The page connects by itself about a minute after the stack is created. Then it checks that the new role works. A new role can take up to two minutes to become usable.

When the account is connected, the step reads Your AWS account is connected and shows the account ID and region. Your AWS account explains what the stack creates, what SendForever can and cannot do, and what to do if the stack fails.

Step 2: Choose your plan

Once the AWS account is connected, the owner picks a plan. You pay once and keep it for life. AWS bills your own account for what you send, at Amazon SES prices.

  • Solo: everything SendForever does, for your own domains, from one account.
  • Company: everything in Solo, with colleagues in your team and a team for each client.

Click Pay followed by the price. Paddle's checkout opens on the page. VAT is added where it applies, and the charge and the invoice come from Paddle. The price shown is the one Paddle charges where you are. After you pay, the step shows "Confirming your payment with Paddle. This takes a few seconds." and moves on by itself.

Only the owner of the team can choose the plan. An admin sees "Only the owner of this team can choose the plan." The plan belongs to the owner and covers every team they own, so a new team you create on the Company plan starts with this step already done.

Step 3: Add the domain you send from

SendForever creates the domain in Amazon SES with 2048-bit DKIM and a custom MAIL FROM, then shows the DNS records to publish.

  1. Under What will it send?, choose Transactional (receipts, password resets, notifications) or Marketing (newsletters, campaigns, announcements).
  2. Enter the Domain, such as example.com, without http:// or an email address. For marketing, use a subdomain such as news.example.com, so mailbox providers score it separately from your transactional email. If you choose Marketing after typing a root domain such as example.com, SendForever changes it to news.example.com for you.
  3. Click Add domain.

If Amazon SES refuses the domain, the form says why. If the domain is already in this team, the form says so. If your team already authorized Cloudflare, the records go into Cloudflare at once. See Domains.

Step 4: Publish the DNS records

This step shows the records your domain needs, each with its purpose beside its type. Publish them at your DNS provider:

  • Add records to Cloudflare: if the domain is on Cloudflare, SendForever adds every record for you. Cloudflare asks you to allow SendForever to read and edit DNS on the accounts you choose, then sends you back to Getting started. You can also click Use an API token instead and paste a token made from Cloudflare's "Edit zone DNS" template for this one zone. The token is used once and never stored.
  • Copy all copies every record at once, to paste into your DNS provider.
  • Send to your DNS admin gives you a link that shows the records to whoever runs your DNS, with no account needed. It works for a week.

When SendForever knows where your DNS is hosted, the card names the provider and, for a known one, links to it. If your provider adds the domain to each name by itself, leave the domain off the end of each name.

Each record in the list shows Verified, Wrong value or Not found. Under a wrong value, Published now: shows what the DNS has instead.

While it waits, the page checks your DNS every 30 seconds. The heading shows where things stand:

  • Publish the DNS records of your domain: some records are not in the DNS yet.
  • Amazon SES is checking your domain: every record is in the DNS. Amazon SES usually sees them within minutes, and at most within 72 hours. The step finishes by itself.
  • Amazon SES could not verify your domain: Amazon SES stopped looking after 72 hours without finding the records. Fix them, then click Verify again.
  • Your domain is verified: mailboxes can now trust email from it.

If Amazon SES has not provided the records yet, the step says they will show in a few minutes. DNS records explains each record.

Step 5: Send yourself a test email

Click Send me a test email. It goes from an address such as [email protected] ([email protected] for a marketing domain) to the address you signed in with, through your own Amazon SES. It also shows in the activity log within a minute.

A new AWS account is in the Amazon SES sandbox, which only delivers to verified addresses. If the sandbox refuses your address, Amazon SES emails it a link to verify it. Open the link, then send the test again. See Leaving the SES sandbox.

A domain sends up to 5 test emails an hour. Click Skip to go on without one. Getting started can finish without the test email.

Step 6: Ask AWS to let you email anyone

A new account starts in the Amazon SES sandbox, where it only delivers to addresses you verified, up to 200 emails a day. This step asks AWS to take it out:

  1. Under What do you send?, choose Transactional, Marketing or Both (sent to AWS as marketing). It starts set to the type of the domain you added.
  2. Check the Website, where AWS can see who you are and what you send. It must start with https://.
  3. Select I only email people who asked for it, and I handle bounces and complaints. Your email address is added as a contact for the review.
  4. Click Send request to AWS.

AWS reviews the request and answers within 96 hours, by email. If AWS declines, the step reads AWS declined production access and offers Request again. Leaving the SES sandbox covers the request and AWS's answer in detail.

If your AWS account already has production access in that region, or a request AWS is reviewing, there is nothing to ask for. Getting started finishes once your domain is verified.

While you wait

Getting started takes about 10 minutes of your own time. The rest is AWS and your DNS working on their own.

  • While the stack is created and its role is checked, stay on the page. It moves on by itself.
  • While Amazon SES checks your DNS records, the step suggests you import an audience or write a template in the meantime. See Audiences and Templates.
  • While AWS reviews your request to email anyone, your part is done. Amazon SES already delivers to verified addresses, so your test emails go out.

Leaving and coming back

Nothing in the app works without the AWS account or before a plan is chosen. Until both are done, the overview brings you back to Getting started.

After that, you can leave at any time and your progress is kept. The team's overview then shows a Finish getting started card with the next step, such as "Next: publish the DNS records of example.com.", and a Continue button that opens Getting started where you left it. Switching to a team that is still getting started also opens its Getting started.

When you are done

Your part is over once the plan is chosen, your domain is verified, and your account can email anyone or has asked AWS to. The page then says how many of the six steps are done, since you can skip the test email. It shows You can now email anyone or Your part is done, with:

  • Open the overview, where you follow how your email does.
  • Import an audience and Write a template.
  • Send yourself a test email, if you skipped it.

If SendForever checks your AWS account again while you are there, for example after you click Check the update, the page shows the AWS account step until the check is over. Then it returns to this screen.

After that, Getting started closes and the app opens on the overview. If AWS later declines your request, the overview shows Finish getting started again, so you can send a new one. Good next pages are Sending email, Audiences, Templates and Campaigns.

Common questions

I did not receive the confirmation code. What can I do?

Check your spam folder, then click Resend code on the Confirm your email page. You can ask for a new code once a minute. A code expires after 30 minutes. If the page sends you back to the sign-up form, the registration expired. Fill in the form again.

Can I sign up with Google?

Yes, with Continue with Google on the sign-up or log-in page, as long as Google has verified your address.

Why can't I see Getting started?

Only team owners and admins go through Getting started. A member is sent to the team's overview. Once the steps are done, Getting started closes and opening it leads to the overview.

The plan step says only the owner can choose the plan. What now?

The team's owner pays for the plan, and it covers every team they own. Ask the owner to sign in and pay on the Choose plan step. The steps after it open once they have paid.

Can I leave Getting started and finish later?

Yes, once the AWS account is connected and the plan is chosen. Your progress is kept, and the overview shows Finish getting started with a Continue button until your part is done.

How long does it take?

About 10 minutes of your own time. AWS creates the stack in a few minutes. Amazon SES usually sees your DNS records within minutes, and at most within 72 hours. AWS answers a request for production access within 96 hours.

My test email was not sent. Why?

In the sandbox, Amazon SES only delivers to verified addresses. If it refused yours, it just emailed you a link to verify it. Open the link, then send the test again. A domain also sends at most 5 test emails an hour, and the message says when you can try again.

Do I have to send the test email?

No. Click Skip. Getting started can finish without it, and the last screen offers Send yourself a test email if you want one later.

I already send with Amazon SES. Do I still go through every step?

Mostly. On the first step, pick the region you already send from. If the account already has production access there, there is nothing to request. Getting started finishes as soon as your domain is verified, and the last screen still offers the test email. Connecting changes nothing for what your app already sends (see Your AWS account).

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