SendForever help
Log in Get started

Help Domains and sending

Domains

A domain is an Amazon SES identity in your own AWS account that you send email from. This page covers how to add a domain, how it is verified, the checks SendForever runs on it, its settings (configuration set, tracking, kept copies, isolation), and how to switch between domains and remove one.

Where domains live

Your team's Domains page lists every domain with its Name, Type (Transactional or Marketing), Status, Checks, Region and Created date. Click a column heading to sort by it. Click a row to open the domain. All domains send from the single AWS region where your team's account is connected. When you open the list, SendForever checks again, one at a time, every domain whose checks are out of date. Until the new result arrives, the domain shows its last status, marked Checking….

Each domain has its own sections: Overview, Activity, Campaigns, Audiences, Templates, Suppressions and Settings. These sections belong to the domain shown in the header.

Team owners and admins can add, change and remove domains. Members can open every domain and read its checks, but cannot change anything.

Add a domain

You need a connected AWS account first (see AWS account).

  1. Open Domains and click Add domain. You can also choose Add domain at the bottom of the domain switcher in the header.
  2. Under What will it send?, choose Transactional (receipts, password resets, notifications) or Marketing (newsletters, campaigns, announcements).
  3. Enter the name in Domain, for example example.com. Leave out http://, and don't enter an email address.
  4. Click Add domain.

SendForever then creates the domain in Amazon SES with the recommended setup:

  • Easy DKIM signing with a 2048-bit key.
  • A custom MAIL FROM domain at mail. followed by your domain, so bounces return to your own domain and SPF aligns for DMARC.
  • Its own configuration set, named sendforever- followed by the domain with dots replaced by dashes (for example sendforever-example-com). The set requires TLS and tracks reputation metrics.
  • Its emails recorded in the activity log, starting with the first one.
  • Isolation from your other domains with an Amazon SES tenant, when your AWS stack is recent enough.

You then land on the DNS records tab of the domain's Settings page, which lists the records to publish. If your team has a live Cloudflare authorization, SendForever adds the records to Cloudflare when the page opens. See DNS records.

Use a subdomain for marketing

Mailbox providers score marketing and transactional mail separately, so a bad campaign should never hurt receipts or password resets. When you choose Marketing after typing a root domain such as example.com, the form suggests news.example.com instead. Like any other domain, a marketing domain gets its own configuration set.

A domain that already exists in Amazon SES

If the identity already exists in your Amazon SES account, SendForever adopts it instead of creating it again. The page then says the domain was already in Amazon SES and that its setup was kept. An existing custom MAIL FROM domain and configuration set stay as they are, and the existing set starts recording to the activity log. If the adopted domain has no custom MAIL FROM, it gets mail. plus the domain. If it has no configuration set, it does not get one; its Configuration set check offers to apply one instead.

Verification

Amazon SES verifies a domain by finding its DKIM records and the MX record of its MAIL FROM domain in your DNS. The status badge shows how far it got:

  • Not checked yet: SendForever has not read the domain yet.
  • Pending: Amazon SES is still looking for the records.
  • Partially verified: either DKIM or MAIL FROM is verified, but not both yet.
  • Verified: both are verified.
  • Temporary failure: Amazon SES could not confirm a record for now and keeps looking.
  • Failed: Amazon SES stopped looking. It gives up after 72 hours without finding the records.

Until the domain is verified, the DNS records tab shows the steps Records published, DKIM verified, MAIL FROM verified and Ready to send. While a check is waiting and the page is open, the page checks the domain again every 30 seconds. Check again, next to the time of the last check, also asks Amazon SES to look at the DNS right away. A message then says which checks changed and which are still waiting.

When the status is Failed, fix the records, then click Restart verification at the top of the page. If the domain uses Amazon SES's own DKIM keys, restarting asks for new keys, so you may get new DKIM records to publish.

A domain is ready to send once no check is failing or waiting. Recommendations and checks that need attention, such as an account still in the sandbox, do not stop it.

The domain's Overview

Overview shows how email from the domain did over the last 30 days, read from your AWS account. Use the dates beside the numbers to pick other days: today, yesterday, the last 7 or 30 days, this or last month, all time, or a range you choose. You can go back 90 days at most, because your S3 bucket keeps the events for 90 days. So All Time also starts no earlier than 90 days ago.

  • Needs attention: what Amazon SES reported about this domain or the whole account and has not cleared yet, with steps to take. See Alerts.
  • Sent, Delivered, Bounced and Complaints. Each is compared with the same number of days before, when those days are within the 90 days. Bounced and Complaints carry a badge (Healthy, Watch it, Too high) for the rate Amazon SES judges. That is the rate of the domain's configuration set once Amazon SES measures the set separately, and the whole account's rate until then. On a card with that badge, the comparison is in the tooltip.
  • Opened and Clicked, shown between Bounced and Complaints when the domain tracks opens and clicks: the share of delivered emails that were opened or clicked at least once.
  • Emails per day, a chart of sent, delivered, bounced and complained-about emails per day.

The numbers are kept for up to 15 minutes. The time they were read appears beside the dates, as Updated 14:05 UTC. Click Update now next to it to read them again. The whole team can do this at most once a minute. A single day is shown hour by hour, from the activity log.

These numbers only count emails that went through the domain's configuration set. An email your app sends through another set is left out. With deliverability insights on, the numbers up to yesterday come from the insights, and today comes from the activity log. The insights only count from the moment they were turned on, so a day the activity log counted more emails on comes from the log. Without insights, or for a range that starts more than 60 days ago, all the numbers come from the activity log, today included. The numbers need a connected AWS account.

If a campaign from the domain started in the last 90 days, a menu beside the dates can show that campaign's numbers instead of all the domain's email. Campaign numbers always come from the activity log. They have no comparison with earlier days and no reputation badge. Bounced then leaves out addresses Amazon SES did not try, the same as the campaign's own report.

To see how one email did, such as a newsletter your app sent, type part of its subject in Subject contains… beside the dates. The numbers and the chart then count only emails that went through the domain's configuration set and whose subject contains those words, ignoring upper and lower case. Like campaign numbers, they come from the activity log, with no comparison and no reputation badge. Pick the day the email went out to see it hour by hour.

The domain's Settings

Settings is where you set up the domain. The header shows its verification status, its type, when it was last checked (with Check again beside it) and which DNS provider hosts it. The main button depends on what the domain needs most: Remove domain if it was deleted from Amazon SES, Restart verification, Add DNS records, Resume sending or Send email. The actions menu next to it has Send email, View activity, a link to the domain's suppressed addresses, Send me a test email (once the domain is ready), Move to another team (when you have a team it can move to) and Remove domain.

Send me a test email sends one email from the domain to your own address through your Amazon SES. You can send up to five an hour per domain. If your account is in the sandbox and your address is not verified, Amazon SES emails your address a verification link first.

The page has five tabs. The first two show how many items are still open on them:

  • DNS records: the records the domain needs and their checks. See DNS records.
  • Configuration: how the domain sends, set in Amazon SES rather than in the DNS. See below.
  • SMTP & API: sending credentials and how to connect your app. See Sending email.
  • Webhook: a URL in your app that receives the events of every email the domain sends. See Webhooks.
  • Reputation: the domain's bounce and complaint rates. When Deliverability insights are on for the account, it also shows their figures, with a By mailbox provider table for the last 30 days: sent, delivered, bounced, complaints, opened and clicked at each provider the domain sent to, largest first, with Other providers last. When DMARC reports come to SendForever, it also shows who sends as the domain according to those reports. The tab appears once the domain is ready to send, or when its DMARC reports come to SendForever or to a mailbox on the domain itself. In the providers table, a dash under Complaints means the provider reports no complaints to Amazon SES. Gmail is one example.

The page opens on DNS records while records wait, and on Configuration once the domain can send.

Problems with the whole AWS account show above the tabs: a sandbox notice with Request production access once the domain is verified (see Production access), an account suppression list that is off (with Enable suppression list), and an account that AWS has put under review or paused.

Checks

Each check has one of these statuses:

  • Passing: nothing to do.
  • Recommended: works, but a better setup is suggested.
  • Optional: an extra you can turn on. It never counts as open.
  • Waiting: waiting on the DNS or on AWS.
  • Needs attention: a problem that does not stop sending.
  • Action needed: something is broken or missing.

The Checks column of the Domains list counts what is open, for example "2 actions needed · 1 waiting", and names the check to handle next. When nothing is open, it says All passing. SendForever checks a domain again when you open its page and its checks are more than five minutes old, every 30 seconds while a check waits on the DNS, and when you click Check again.

Checks on the DNS records tab

  • DKIM signing: Amazon SES signs the domain's emails. It waits until the three DKIM records are found and fails if Amazon SES cannot find them. With a 1024-bit key it is a recommendation: rotate to 2048-bit in the Amazon SES console.
  • Custom MAIL FROM (SPF alignment): bounces return to mail. plus your domain. If Amazon SES cannot find its MX record, emails fall back to amazonses.com and SPF does not align.
  • DMARC policy: the domain publishes a DMARC record with a policy and a report address.
  • SPF on the domain itself: the domain publishes exactly one SPF record. With no SPF record it is a recommendation. With two or more it fails, because receivers treat that as having no SPF. A record with something invalid in it, such as -all., or one that takes more than 10 DNS lookups to check, needs attention but does not stop the domain from sending. See DNS records.
  • Domain can receive replies: the domain has an MX record, so replies and mail to postmaster@ do not bounce.
  • Brand logo (BIMI): appears once DMARC is at p=quarantine or p=reject. It reads the domain's BIMI record.

DNS records explains each record and how to fix each check.

Account and identity checks

  • Production access: the account can send to any recipient. In the sandbox the account only delivers to verified addresses. The check then needs attention, but the domain can still send tests.
  • Account suppression list: addresses that bounce or complain are suppressed. It fails unless the list is on for both bounces and complaints. Click Enable suppression list to fix it.
  • Account standing with AWS: fails when Amazon SES has paused the account, or has put it under review because of bounces or complaints. For a review, answer the case in the AWS Support Center.
  • Domain exists in Amazon SES: fails when the identity was deleted from Amazon SES. Remove the domain in SendForever and add it again to recreate it.

Configuration

Owners and admins change these settings on the Configuration tab. Each change is made in Amazon SES right away, and the domain is checked again. If AWS refuses a change, That change was not made appears above the checks with AWS's reason, and the page scrolls to it.

Sender name

Sender name is the name inboxes show beside the address, such as Example News. Enter it and click Save. New campaigns and test emails from the domain start with this name. An email your own app sends uses the name your app gives it.

Encryption and the domain's own configuration set

Encryption shows Required when every email is delivered over an encrypted connection, or Not required when Amazon SES delivers unencrypted to a server that cannot encrypt.

The Configuration set check passes when the domain sends through its own configuration set, with TLS required and reputation metrics on. It fails when no configuration set is attached or TLS is optional. It is a recommendation when reputation metrics are off or the domain shares a set with other domains. Apply recommended settings creates or updates sendforever- plus the domain with dashes, attaches it to the domain and records its emails in the activity log. A domain that moves off a shared set keeps what that set did for it: open and click tracking and kept copies carry over, and the old set is not deleted. Two domains whose names produce the same set name, such as a-b.com and a.b.com, cannot both have their own set in one account. The page names the domain that already owns it.

If emails sent after such a move still name the old set, Old configuration set still in use needs attention. To fix it, name the domain's own set in your app, or no configuration set at all. The SMTP & API tab shows how.

Opens and clicks

The switch beside Opens and clicks turns tracking on or off for everything the domain sends. With tracking on, Amazon SES adds a pixel and rewrites every link. The activity log then shows when each email was opened and which link was clicked, and the webhook can post these events. With tracking off, emails go out exactly as written. Tracking is only offered on the domain's own configuration set.

If Deliverability insights (Amazon SES Virtual Deliverability Manager) are on, this switch also turns their engagement metrics on or off for the domain's configuration set. Deliverability insights themselves have one switch for the whole account, on the AWS account page, because AWS bills them for the whole account.

Links host gives the domain a host of its own for its links: the unsubscribe links in its campaigns, the subscriptions API your app calls, and its tracked opens and clicks, which otherwise use Amazon's shared tracking domain. Every link then shows your own domain. The setting is offered once the domain is on its own configuration set. It is a recommendation while the domain tracks opens and clicks without a links host. Enter a host of the domain that nothing else uses (links. plus your domain is suggested; the MAIL FROM domain is not allowed) and click Use this host. SendForever then:

  1. Asks Certificate Manager for a certificate, which needs the Links host certificate CNAME record.
  2. Sets up a CloudFront distribution in your AWS account, which takes up to a quarter of an hour.
  3. Waits for the Links host CNAME record that points the host at the distribution. Then it has Amazon SES write tracked links with the host over HTTPS, and hands out unsubscribe links on it.

It takes about half an hour in all. SendForever does everything in your AWS account. Your part is the two CNAME records. When one is needed, the setting says Your turn and the page scrolls to DNS changes waiting to be published. If the domain's DNS is at Cloudflare, click Apply all pending DNS changes in Cloudflare. Otherwise, View the changes opens the DNS records tab.

If the domain publishes CAA records, one of them must allow Amazon, with flags 0, tag issue and value amazon.com. Otherwise Certificate Manager refuses the certificate. SendForever checks this before asking for a certificate and says what to add. It checks again while the host is in use, because Certificate Manager renews the certificate under the same records. If a CAA record added later leaves Amazon out, the setting turns to Attention. If a certificate was refused for this reason and the domain's DNS is at Cloudflare, Apply in Cloudflare adds the record and sets the host up again.

CloudFront gives a host to one distribution only. If a links host left its distribution in your AWS account, for example when the domain was removed from SendForever only and added again, SendForever takes that distribution over with the new certificate. If anything else already answers for the host, such as another email service's tracking host, the setup fails and says the host is already in use. It names where your DNS points the host, or the distribution in your AWS account that holds it. CloudFront also refuses a host whose DNS record still points at another CloudFront endpoint, even one that no longer exists, as after a links host was stopped: delete that DNS record first. Remove the host from that service and click Use this host again, or type another host in the field under the reason and click Use this host. The same host keeps a certificate that was already issued. A different host gets a certificate of its own.

A host that failed keeps its records on the DNS records tab until you stop using it. The setup moves forward each time SendForever reads the domain, so keep the domain's page open or come back to it. A host set up before your stack reached version 16 gets the unsubscribe links and the API the same way once the stack is updated.

To go back, click Stop using followed by the host. Amazon SES goes back to tracking on its own domain right away. The distribution and certificate are taken down over the next few minutes as SendForever reads the domain. The host's Links host DNS record has to go too, because CloudFront will not set the same host up again while that record points at the old endpoint. With a live Cloudflare authorization SendForever removes it at once. Otherwise the DNS records tab marks it Remove for you to delete at your DNS provider. The Links host certificate record can stay. Once the host's endpoint is gone, links in emails already sent through the host stop working, and so do calls to the subscriptions API on it. Unsubscribe links must keep working for 30 days after a campaign. So you cannot stop the host while a campaign from the domain is scheduled or sending, or for 30 days after the last one. The page says from when you can.

Copies of sent emails

The switch beside Copies of sent emails keeps a copy of every email the domain sends, as delivered, for three months. The copies go to a Mail Manager archive named sendforever-messages in your AWS account. You can then open any message in the activity log and read it. It costs $2 per GB archived plus $0.19 per GB a month, about a dollar per ten thousand typical emails. If you turn it off, what was already archived stays until its three months are up. This setting needs the domain's own configuration set.

The first time an account keeps copies, Amazon SES needs its service-linked role, AWSServiceRoleForAmazonSES. AWS makes this role once per account. A stack from version 23 lets Amazon SES make it. On an older stack, the page says Your AWS account needs a role Amazon SES makes once and gives a command to run in CloudShell, in the AWS console, before you try again:

aws iam create-service-linked-role --aws-service-name ses.amazonaws.com

Bounce and complaint emails

By default, Amazon SES emails every bounce and complaint to your sender address. If you turn off the switch beside Bounce and complaint emails (Email me each bounce and complaint), they are recorded in your CloudWatch instead. Addresses that bounced are listed under Suppressions. If the emails are off but nothing records bounces and complaints, the check is a recommendation. Record them in CloudWatch fixes it.

Domain isolation

Isolating a domain gives it its own Amazon SES tenant, with its own reputation, pause switch and suppression list. A problem on another domain then cannot pause it. The tenant is named after the domain with dots replaced by dashes. So, as with configuration sets, a-b.com and a.b.com cannot both be isolated in one account. New domains are isolated from the start. For any other domain, click Isolate this domain. The app quotes isolation at $0.005 per 1,000 emails the domain sends, on top of the $0.10 per 1,000 that Amazon SES charges to send them. If a domain is the only one in its account, it passes this check, since there is nothing to isolate it from yet.

Isolation only applies to emails that name the tenant. Add the header shown on the tab, X-SES-TENANT: followed by the tenant name, to every email you send from the domain. Isolation header reads the last 7 days of the activity log. It needs attention when some emails did not have the header, and turns green after 7 days in which every email has it.

Once isolated, the tab offers:

  • Automatic pausing: Pause on serious problems (recommended), Pause on any problem or Never pause on its own. The first is what Amazon SES gives every new tenant. With Never pause on its own the check is a recommendation, because a domain that keeps sending through a serious problem can get the whole account paused.
  • Pause sending and Resume sending: Amazon SES refuses the domain's emails until you resume. Other domains keep sending. A paused domain is not ready to send.
  • Stop isolating: the domain goes back to sharing the account's reputation and suppression list. Its own suppression list is deleted, and emails that still name the tenant are refused. The templates the tenant held stay in your account and are shared with the domains that are not isolated.

When Amazon SES finds a problem with an isolated domain's sending, the check needs attention and quotes what Amazon SES reported.

Switch domains

The domain switcher is in the header of every domain section. Click the domain's name to open its Overview, or the arrow beside it (Switch domain) to pick another domain. You stay on the same section: switching from Activity opens the other domain's Activity. From a single template, audience or campaign, you land on that section's list for the other domain. Opening a link to a domain's page switches to that domain. Each browser remembers its own choice for each team. Without a saved choice, the first domain by name is shown.

Remove a domain

Click Remove in the domain's row on the Domains page, or Remove domain in the domain's actions menu. You cannot remove a domain that still has audiences. The dialog names them, and you remove them on the Audiences page first. Choose how far to go:

  • Remove from SendForever only: keeps the Amazon SES identity, the sending credentials and every DNS record. Sending keeps working. The domain's subscription keys are revoked, so your app can no longer add people through them, and its webhook is removed, so your app stops receiving its events.
  • Delete everything SendForever created: revokes the sending credentials and the subscription keys, removes the domain's webhook, its tenant, its own configuration set and its brand logo, and deletes the identity from Amazon SES. Type the domain's name to confirm. Anything still sending as the domain stops at once. This cannot be undone. A domain with a links host must stop using it first, in its configuration, so its CloudFront distribution and certificate are removed too.

When you delete everything, SendForever removes the DKIM, MAIL FROM and brand logo records from Cloudflare if it is authorized there. It removes each record only while it still holds the value SendForever published. Without a live authorization, tick Also remove its DNS records from Cloudflare and click Continue to Cloudflare. If the domain's DNS is elsewhere, leave it unticked and remove the records by hand. DMARC and the SPF record on the domain itself always stay, because they protect the domain whether or not you send from it. The domain's configuration set is not deleted.

Deleting everything needs a connected AWS account. Adding the domain again later creates a new identity with new DKIM records to publish.

Move a domain to another team

Owners and admins can move a domain to another team they own or administer, when that team has an AWS account connected and does not have the domain yet.

  1. On the domain's Settings, open the actions menu and click Move to another team.
  2. Choose the team and click Move. SendForever adds the domain to that team's AWS account and opens it there.
  3. Publish the DNS records it shows. Its DKIM records are new. The MAIL FROM records stay the same unless the other account is in another region.
  4. Once it is verified there, remove it from the old team. Until then, both teams send as the domain, and each team's page says the other team still has it.

What moves with it:

  • Its DMARC, senders, MAIL FROM and forwarding choices.
  • Its DMARC reports, which go on arriving with no DNS change. Reports received before the move stay with the old team.
  • Copies of its templates: an isolated domain's own templates, or the account's templates that no other domain holds. If the other account already has a template with the same name, that template is left as it is, and the page says so.
  • Opens and clicks tracking, and its brand logo.

What stays with the old team: its audiences and their contacts, campaigns and activity, sending credentials (create new ones in the new team) and the links host. You can set up a links host in the new team once the old team has removed it. The old team can only remove it 30 days after its last campaign, so unsubscribe links keep working.

To remove the domain from the old team, remove its audiences there first, then remove the domain. Delete everything SendForever created leaves in place the Cloudflare DNS records that the new team's domain still uses.

Common questions

Why does my domain still say Pending?

Amazon SES has not found the DKIM records or the MAIL FROM MX record yet. It usually finds them within minutes, and within 72 hours at most. Check that each record on the DNS records tab shows Verified, then click Check again to ask Amazon SES to look right away. DNS records explains the statuses and the common mistakes.

My domain says Failed. What now?

Amazon SES stopped looking after 72 hours. Fix the records the tab marks as Not found or Wrong value, then click Restart verification. If new DKIM records appear, publish them too.

Can I send while some checks are only recommendations?

Yes. A domain is ready to send when nothing is failing or waiting. Recommendations, optional extras and checks that need attention, such as the sandbox, do not stop it.

Should I add my root domain or a subdomain?

Add the root domain for transactional email and a subdomain such as news.example.com for marketing. Mailbox providers score the two separately.

The Configuration set check says my domain shares a configuration set. Is that a problem?

On a shared set, tracking, kept copies and the reputation numbers are decided for all the domains on that set together. Click Apply recommended settings to give the domain its own set. What the shared set did for the domain carries over, and the shared set is not deleted.

Why does isolation say only some emails named the tenant?

Isolation only counts for emails that carry the X-SES-TENANT header with the domain's tenant name. Add the header everywhere your app sends email. The SMTP & API tab shows how.

Why don't I see Track opens and clicks or Keep copies?

These settings belong to the domain's own configuration set. A domain with no set, or on a shared set, is not offered them. Apply the recommended settings first. Kept copies and a links host also need a recent enough AWS stack.

Who can change a domain?

Team owners and admins. Members can read every check but cannot add, change or remove domains.

Does removing a domain stop my emails?

Remove from SendForever only does not. The identity, credentials and records stay, and sending continues. Delete everything SendForever created stops anything sending as the domain immediately.

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