Skip to main content

Sending email from your domain

Your app sends its users two sign-in emails: a confirm your address message when somebody signs up, and the reset link behind "Forgot password". These are the two your sign-in flow can't work without and can't send on its own.

Connect a sending domain and both go out from an address of yours — noreply@notify.yourbrand.com — signed with your domain's own key. Your users see your domain in the From line and in the message headers; Berrybell's name appears in none of them. You hold no email provider account, and your app holds only a Berrybell send token that can request those two messages.

The same domain also sends your app's email templates, once you've written and published them: an order confirmation or a booking reminder, for example. They have their own token and their own section in Cloud → Email, under What this app sends. Notifications to you don't use your domain at all. Berrybell sends them, on every plan, with no setup.

Until it's set up

"Forgot password" on your live app is refused — there's nowhere to send the link. Signing in still works normally and always will: a confirmed address has never been required for it. So this isn't a feature you've yet to add; it's a button already on your sign-in screen that currently does nothing.

Before you start​

  • A domain you own, and access to its DNS settings at your registrar (GoDaddy, Namecheap, Cloudflare, Google Domains, and so on).
  • A paid plan. Sign-in for your app's users is itself a paid-plan feature (see What has to be true first), and sending domains aren't available on the free tier either.
  • The workspace Admin role to set up, change or remove anything on this page. Editors can view it.

Set it up​

Open Project settings → Cloud → Email. There are two tabs, Domain and Sender. The page opens on Domain until your domain is verified, and on Sender after that. If Berrybell can't offer the setup — on a free workspace, for example — there are no tabs and nothing to fill in.

On a project with environments, select production in the top bar first. The sending domain is set up and changed only while production is selected — see Environments and the preview.

On the Domain tab​

  1. Under Set your sending domain, enter the domain you own in Your domain — yourbrand.com. Subdomain (required) is prefilled with notify, and a line under the fields previews the address your mail will come from: noreply@notify.yourbrand.com.
  2. Before anything is created, Berrybell reads _dmarc.<sending domain> — here _dmarc.notify.yourbrand.com — and Set domain stays disabled until that check answers. What it finds decides whether a DMARC record is on offer (see Subdomain or root domain):
    • Nothing published there. An unticked checkbox appears: Also give me the DMARC record for _dmarc.notify.yourbrand.com. Tick it if you want a p=none record in your list; leave it and you won't be asked for one.
    • A policy already there. You're told it already covers this mail, and no DMARC record is asked for.
    • The lookup fails. Attaching is refused until Check again gets an answer.
  3. Press Set domain. The panel says Add these N records — normally five: three DKIM CNAMEs, plus an MX and an SPF TXT record on bounce.<sending domain>. It's six if you asked for the DMARC record. Add them at your registrar exactly as shown. Copy all copies the whole set, and an N of M copied tally keeps track as you copy them one by one. The status then updates on its own, with DKIM signing, Bounce domain and DMARC as separate rows so you can see which is outstanding. Berrybell checks about once a minute; Check now asks again right away, unless the domain was checked in the last 30 seconds (by you or automatically) — then it tells you how many seconds to wait.

On the Sender tab​

  1. Once the domain is attached and sign-in is turned on, set your From address — you don't have to wait for verification. Right after you attach the domain it's prefilled with noreply@<sending domain>; on a later visit that address is only the placeholder, so type it in. It has to be an address exactly at the sending domain: hello@notify.yourbrand.com works, but hello@yourbrand.com and hello@team.notify.yourbrand.com don't. The mailbox doesn't have to exist to send, but replies go to it, so one somebody reads is worth setting up. Add a Sender name (optional) if you want one in the From line, then press Turn on email (the button reads Save sender when you change it later).
  2. Publish your project. Your app is given its email settings when it's published, not when they're saved. Until you publish, the page shows Publish this project to turn the emails on, and your live app sends nothing.
  3. Once the domain is verified, press Send myself a test. It goes to your own Berrybell account address and proves a message from your address was accepted — not that it arrived: it can still land in spam, or bounce minutes later. It counts toward the limits like any other send.

A dot on a tab means that half has something waiting for you.

Do the domain first

The Domain tab doesn't need sign-in turned on — set it up and get the records published straight away. DNS is the only part with a wait in it, so starting it before you turn on sign-in means there's nothing to wait for afterwards.

The Sender tab is the half that needs sign-in on: the From address exists to send verification and password-reset mail, so there's nothing for it to do until those flows are enabled. Your domain keeps verifying either way, and stays verified.

Template emails don't need sign-in at all. Their sender is set separately, under What this app sends (see The sender).

Subdomain or root domain​

notify.yourbrand.com is the default and the recommendation. yourbrand.com itself is supported — tick Send from yourbrand.com itself, with no subdomain in front of it on the Domain tab, and a warning about reputation appears before you attach — but it's the sharper-edged choice, and it's worth a minute before you pick it.

Reputation is the part you can't undo. On a subdomain, a bounce spike from your signup form damages notify.yourbrand.com and nothing else. At the root it damages yourbrand.com — the domain your invoices, your sales email and your support replies go out from. Sending subdomains are why you see em., mail. and e. prefixes in your own inbox from companies much larger than yours.

You can't fix that later by editing DNS. Everything else about root sending you can.

Your existing DMARC policy is safe either way. This used to be the reason root sending wasn't offered at all. A DMARC policy lives at _dmarc.<sending domain>: on notify.yourbrand.com that's usually a name nobody has published at, but on yourbrand.com it's your organisation's own policy — and the only record we'd offer says p=none. Writing that over an existing p=reject would silently weaken spoofing protection for all your mail, and nobody would notice until someone got spoofed.

So on every attach, subdomain or root, Berrybell looks first, before creating anything:

What we find at _dmarc.<sending domain>What you're asked to add
A policy already thereNo DMARC record. Yours already covers this mail; we don't touch it.
NothingNormally five records by default, none of them DMARC — we leave _dmarc empty. Tick the box for a sixth, a p=none record. On a root domain that record is your organisation's policy for all its mail — p=none is better than no policy at all, but it would still be us setting policy for your whole domain, so you decide.
We can't look it upNothing. The attach is refused until Check again gets an answer — we won't guess.

The DKIM, MX and SPF records never collide, on either rail. The DKIM records are selector-scoped, so they sit alongside Google Workspace's or Microsoft 365's without touching them, and the MX and SPF records go on a bounce. subdomain of the sending domain. If your mail runs on yourbrand.com, this setup does not go near it.

Already on a subdomain?

Nothing changes and there's nothing to do. No migration, no re-verify.

What the records do​

You don't need to understand these to add them, but if you'd like to know:

RecordsPurpose
CNAME (normally 3)DKIM. Let Berrybell sign mail as your domain, so receivers can verify it really came from you.
1 × MXBounce routing. Where delivery failures and complaints come back to.
1 × TXTSPF, for the bounce subdomain.
1 × TXTDMARC, telling receivers what to do with mail that fails those checks. Only when you ask for it at setup, and only if nothing is already at _dmarc.<sending domain>; when it's omitted, a note under the records says why.

Together they're what stops your app's mail landing in spam. Verification needs the DKIM and bounce records; a DMARC record isn't required for it.

To add a DMARC record later, remove the domain and attach it again, ticking the box that time. That issues new DKIM records too, so the whole set changes.

How long it takes​

DNS changes usually appear within a few minutes to a few hours, though some registrars take longer. Berrybell checks on its own about once a minute, so there's nothing to watch. If you've just published a record, Check now asks again — unless the domain was checked in the last 30 seconds.

Owners and admins of the workspace are emailed when the domain verifies, when setup fails and when sending is paused.

Setup doesn't wait forever. Verification gets 72 hours from when you attach the domain:

  • Records not found. If Amazon hasn't confirmed either the DKIM records or the bounce records after 72 hours, the setup is cancelled and the domain removed, and owners and admins get an email setup expired message. Attach it again to start over.
  • Amazon gives up. If Amazon, which Berrybell sends through, stops waiting before the records verify, the domain shows Setup failed — "Amazon stopped waiting for these records". Checking again can't restart it: use Remove domain, attach it again, and publish the new records. They won't be the same ones, because a fresh setup gets fresh DKIM keys.

If it doesn't verify​

Nearly every failure is one of these four:

Your registrar added the domain name twice. Some providers append the zone name to whatever you type, turning abc123._domainkey.notify.yourbrand.com into abc123._domainkey.notify.yourbrand.com.yourbrand.com. Check the saved record — if the domain appears twice, enter just the first part instead.

A CNAME is proxied. On Cloudflare, the DKIM records must be DNS only (grey cloud). An orange cloud makes them resolve to Cloudflare instead of to Berrybell, and verification never completes.

Only some records were added. Every DKIM and bounce record the panel lists has to be live. One short looks almost right and never verifies — the panel's copy checklist is there to help you keep track. The list the panel shows is the whole set. If it has no _dmarc row, a note under the records says why — your domain already had a policy, or you didn't ask for one — so don't add one by hand without checking what's already published at that name.

There's already an MX record on the bounce subdomain. There can only be one. Remove the other MX record, or remove the domain and attach it again with a different Subdomain.

What the status means​

A pill at the top of Cloud → Email sums up the project's email:

PillMeaning
SendingThe domain is verified, a From address at it is saved, and sign-in is on. If the Publish this project to turn the emails on banner is showing too, your live app gets the settings on its next publish.
DNS not finishedThe domain is attached and still waiting for its DNS records. The checks on the Domain tab show which is outstanding.
Saved — untestedA sender is saved, but nothing has proved it can send yet. If your From address was carried over from an email provider connected before sending domains existed and sits outside your sending domain, every send is refused and the page says so — change it to an address at the domain. Otherwise, send yourself a test.
Setup failedVerification timed out. Remove the domain and attach it again — see How long it takes.
PausedAmazon paused sending after a reputation finding — usually bounces to addresses that don't exist, or complaints from recipients. The reason Amazon gave, if any, is shown. Your DNS is fine and nothing needs re-doing. It affects only this project (its sign-in emails and its template emails alike), and sending resumes on its own once Amazon lifts it. If you don't know what caused it, contact support before attaching anything new.

With nothing set up yet, or while something blocks setup, there's no pill; the page says what to do instead.

On the Domain tab, a second pill beside the domain name shows where verification is:

PillMeaning
Add the DNS recordsAmazon hasn't confirmed the DKIM or the bounce records yet. Nothing is in progress until you publish the records.
Checking DNS…Some of the records have been found, or Amazon is retrying, and verification is under way.
VerifiedDKIM and the bounce domain are verified.
Setup failedAmazon stopped waiting after 72 hours.
Paused by AmazonSending is paused, as described under Paused above.

Changing or removing it​

On the Sender tab, once a sender is saved:

  • Change sender edits the From address or sender name. There's no DNS to redo.
  • Replace token gives your app a new send token. The old one stops working at once, and your published app is still holding it, so verification and password-reset emails stop until you publish again. Only do this if the token has leaked.
  • Stop sending turns the emails off. "Forgot password" on your app stops working, and so does a forced password reset, which relies on the same flow. Nobody is signed out and no account is deleted, and your sending domain stays attached and verified. On a project with environments, this stops email in every environment too, because they all send from production's sender. Template emails have a sender of their own, and carry on.

On the Domain tab:

  • Remove domain stops verification and password-reset emails immediately and clears your From address, and the DNS records you published stop doing anything. Your template emails stop too, until a sending domain is verified again. Attaching the same domain again later gives you a different set of records, because the DKIM keys are new every time. On a project with environments, it stops email in every environment too.

What this sends, and how much​

For sign-in, two transactional messages to your own end users: the confirm your address email at sign-up, and the password-reset link. Your app asks for one of those two by name and Berrybell writes the message. Your app never hands over a recipient, a subject or a body.

The domain also sends your email templates, and they don't loosen that. Each template's wording is fixed, and checked by Berrybell, before its first send. Your app only fills in typed details such as a date or a booking reference, never a sentence or a link, and every template email carries an unsubscribe link.

There's no way to send arbitrary email through it. That's deliberate: it's what stops the sending address becoming a route for newsletters or campaigns, and it's why your domain's reputation stays tied to mail your users actually asked for.

The sign-in emails' wording is fixed, and the only thing in it that's yours is your project's name. For a project called Acme, the subjects are "Confirm your email for Acme" and "Reset your Acme password". Both links expire after one hour. In apps built from a template that comes with sign-in, a completed password reset also signs that account out of its other sessions. To see exactly what your users get, open the preview of either email in Cloud → Email. Nothing is sent.

Limits​

Per project, per rolling window. The Sender tab shows the caps and how much of them you've used — for example "Auth mail only. 60/hour, 500/day · 12 sent in the last 24h".

  • 60 an hour and 500 a day per project, by default.
  • 5 an hour to one address. One recipient gets at most 5 auth emails an hour from one project.
  • Attempts count whether or not they're delivered. A message Amazon refuses — a bad address, for example — uses up the allowance just as a delivered one does. Test sends count too.
  • Each environment gets the same caps in a window of its own — see Environments and the preview.
  • Template emails have limits of their own, and don't use these.

Marketing email (newsletters, promotions, announcements) isn't supported.

Environments and the preview​

A project has one sending domain, shared by every environment. Once you have another environment, production's Email page says so: "One sending domain is shared by all your environments." You set it up and change it only while production is selected; with another environment selected, Cloud → Email shows the shared domain and whether it's ready to send.

In every other environment, sign-in email is off until you turn it on there: select the environment in the top bar and press Send email from this environment in Cloud → Email. Until then, "Forgot password" fails in that environment. Turning it on is refused until:

  • sign-in is turned on for the project, and
  • production's sending domain is verified and not paused, with a From address at it.

A project that still sends through an email provider connected before sending domains existed has to set up a sending domain first — only a sending domain can be shared.

Once it's on, the environment sends the same two emails, from the shared domain, to its own users, with links to its own sign-in address (see Sign-in in other environments). It has its own caps, the same numbers as production counted separately, so testing there can't use up production's allowance. It does spend the shared domain's reputation, though: bounces and complaints from an environment count against the domain your live app sends from.

The change reaches the app the next time you publish to that environment — the page says "Publish to this environment to start sending." Stop sending from this environment takes effect at once.

The preview never sends sign-in email

The automatic preview and the dev server never send sign-in email, whichever environment is selected — including on a project with only production. As Cloud → Email puts it: "Sign-in email, Google and SSO don't work in the preview or the dev server. Publish to an environment to test them."

Notifications to you and template emails are different. The preview, the dev server and every environment can send them without being turned on there, but only to your own team: notifications go to owners and admins, and template emails go to members of your workspace. See Outside production.