> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useboom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Email setup for your IT team

> What to add so Boom can send as your domain and receive a copy of your support email, what it doesn't change, and how to undo it.

This page is for whoever manages your company's DNS and email. Someone on your
team may have sent you the same information from Boom with **Send to IT** (in
**Settings › Email**): plain text with your
organization's own Boom address, missing DNS records and provider steps filled
in. If it came by email, reply to it to reach the person who sent it.

There are two independent pieces. Your team may ask for one or both.

| Piece | What you change | Why |
| - | - | - |
| [Send as your domain](#send-as-your-domain-dns-records) | A few DNS records | Emails from Boom go out as `hola@yourcompany.com` and pass inbox checks |
| [Support address copy](#support-address-copy) | One rule in Google Workspace or Microsoft 365 | Emails to `support@yourcompany.com` also reach Boom's inbox |

Boom never gets access to your mailbox: no password, no sign-in, no API
access. It only receives the copies your rule sends.

## Send as your domain: DNS records

In **Settings › Email**, the **Your domain** row lists the exact records for
your domain. Each record has a labelled **Name** and **Value** with a copy
button, and a **Found** / **Not found yet** status. Copy the names and values
from there; they are specific to your domain. The last value you copied stays
marked **Copied**, so you can see where you left off when you come back from
your DNS host.
Your domain uses one of two sets of records, depending on how it was
connected. Boom shows only the set that applies, and you can tell them apart by
the DKIM record's name.

**Records with `resend._domainkey`:**

| Shown in Boom as | Record | What it does |
| - | - | - |
| Sending | SPF (TXT) | Authorizes Boom's mail servers to send for your domain |
| Signing | DKIM (TXT, at `resend._domainkey`) | Public key that inboxes use to check each email's signature |
| Policy | DMARC (TXT) | Your policy for email that fails the checks above |
| Bounces | MX, on a `send` subdomain | Returns bounce notices to Boom's mail servers |
| Bounces | SPF (CNAME) | Return path for bounces |

**Records with `boom1._domainkey`:**

| Shown in Boom as | Record | Name | Value |
| - | - | - | - |
| Signing | DKIM (CNAME) | `boom1._domainkey` | `boom1.<your key>.dkim.mail.useboom.tech` |
| Signing | DKIM (CNAME) | `boom2._domainkey` | `boom2.<your key>.dkim.mail.useboom.tech` |
| Bounces | MX, priority 10 | `send` | `feedback-smtp.us-east-1.amazonses.com` |
| Sending | SPF (TXT) | `send` | `v=spf1 include:amazonses.com ~all` |
| Policy | DMARC (TXT) | `_dmarc` | `v=DMARC1; p=none;`, possibly followed by `rua=mailto:…;` (only if your domain has no DMARC yet) |

The two DKIM records are CNAMEs, not TXT: they point at signing keys Boom
keeps, so Boom can rotate a key without asking you to change DNS again. Add
both; the second is the slot for the next key. Boom checks only the first,
so the second shows the same status as the first: double-check you added it. If your DNS already has the
`send` MX and SPF records from the `resend._domainkey` set, they are the same
records: keep them. The `send` records must be in place before Boom sends anything:
without them, mailbox providers would bounce the mail, so Boom waits for
them instead.

> [!WARNING]
>
> On Cloudflare, set every CNAME record Boom lists to **DNS only** (grey cloud),
> not **Proxied** (orange cloud). A proxied CNAME answers with Cloudflare's own
> addresses instead of pointing at Boom's signing key, so the record shows
> **Not found yet** and inboxes can't check your emails' signatures.

If a subdomain is connected (for example `mail.yourcompany.com`), the names
include it (`boom1._domainkey.mail`, `send.mail`, `_dmarc.mail`): Boom shows
them relative to your root domain, the way most DNS hosts ask for them. A
DMARC record on your root domain already covers the subdomain: with the
`boom1._domainkey` set the **Policy** record then shows **Covered by yourcompany.com** and
there is nothing to add. Don't add a separate `p=none` record for the
subdomain; it would weaken your root domain's policy there.

Your domain needs only the records Boom lists. Then click **Check now** in
the row; DNS changes can take up to 24 hours to show up. Each record shows
**Found** or **Not found yet**, so you can see which one is missing. With the
`boom1._domainkey` set, a record that is already in your DNS but not yet confirmed shows
**Found, confirming…**, and a line under **Check now** sums up the check
(for example "Checked just now: 4 of 5 found"). Confirmation usually takes a
few minutes; while the row is open, Boom checks again on its own and the
domain turns **Verified** without reloading the page. Checks for the
`boom1._domainkey` record stop after 72 hours:
if it still isn't found, fix the record, then click **Check now**, which
starts a new 72-hour window (the record name and value stay the same).

### What these records do NOT change

* **Your main email is untouched.** The MX record is on a subdomain
  (`send.yourcompany.com`, used only for bounces), not on your root domain.
  The MX records that deliver mail to your mailboxes stay as they are.
* Nothing is removed or replaced. Add each record at the name Boom shows.
  If your domain already has a DMARC record, keep it rather than adding a
  second one.
* If another email service already has records at `send.yourcompany.com`,
  Boom shows a warning listing them. Don't delete them (that service uses
  them for its own bounces) and don't add a second MX next to them: contact
  Boom instead. Records that already match the ones Boom shows are fine.
* Don't skip the DMARC record. Gmail, Yahoo and Microsoft send bulk email
  without one to spam or reject it; see [Email deliverability](https://docs.useboom.ai/email-deliverability.md).
* Copy the DMARC value exactly as Boom shows it. When it ends in
  `rua=mailto:…`, mailbox providers that support it send Boom a daily summary of the email
  sent with your domain's name, which helps spot mail that fails the checks.
  If you already have a DMARC record, you can add that `rua=` address to it
  next to your own.

**Gmail spam reports (optional, `boom1._domainkey` set only).** Boom may also
list a **Gmail** TXT record at your domain's own name, with a value starting
`google-site-verification=`. It only proves to Google that the domain is yours,
so Boom can see in Google Postmaster Tools how many Gmail users mark your
emails as spam. Sending doesn't depend on it, and it shows **Pending**
until Google confirms it. Keep it in place afterwards: Google checks it again
from time to time.

Open and click tracking, if your team turns it on, needs one more CNAME on a
tracking subdomain. That applies only to domains with the `resend._domainkey`
records. Domains with the `boom1._domainkey` records have no tracking record
to add: Boom tracks their marketing email itself once it has turned tracking
on for the workspace. See [Email tracking](https://docs.useboom.ai/email-tracking.md).

### If the domain is in another email account: the claim record

This applies only to domains that use the `resend._domainkey` records. Those
domains send through Resend, and a domain can be set up in only one Resend
account. If yours is already in another one (your company's own, or a tool
someone set up before), Boom asks your team to **claim** it, and you get one
extra TXT record to add first, at the root of the domain (some DNS hosts write
it as `@`).

> [!WARNING]
>
> Adding the claim record is what moves the domain to Boom. Once the claim
> completes, anything that sends email from your domain through that other
> account stops working, and deleting the record afterwards does not undo it.
> Check that nothing still relies on that account before you add it.

After the claim completes, Boom lists the usual records. Your DNS already has a
`resend._domainkey` record from the other account: **replace its value** with
the one Boom shows. Don't add a second one.

## Support address copy

Boom gives your organization its own receiving address, for example
`acme-k7q2x9@reply.useboom.ai` (shown in **Settings › Email**, in the
**Support address** row and under **Advanced settings**). You add a rule that sends a **copy** of email for your support
address to it. Delivery to your own mailbox doesn't change.

* **Google Workspace:** a routing rule (Admin console →
  **Apps → Google Workspace → Gmail → Routing**) for inbound email whose
  envelope recipient is the support address, with **Also deliver to** the Boom
  address.
* **Microsoft 365:** an Exchange mail flow rule (**Mail flow → Rules**) that
  applies when the recipient is the support address and **adds the Boom
  address to the Bcc box**. Use a mail flow rule: Microsoft 365 blocks
  automatic forwarding to outside addresses by default, so mailbox forwarding
  or an Outlook rule would need a change to the outbound spam policy
  (**Microsoft Defender → Anti-spam policies**) as well.
* **Gmail** (a single inbox): a forwarding address plus a filter.

Full steps: [Connect your support address](https://docs.useboom.ai/email-support-address.md).

Once the rule is in place, someone with settings access in Boom can click
**Send test** on the **Support address** row to confirm it: the result shows within 90 seconds. A new
Workspace routing rule or Microsoft 365 mail flow rule can take up to an hour
to start working.

### The daily check email: allow it

Once a day Boom sends one email to the support address to confirm the copy
still works:

* **Subject:** `Boom forwarding check`
* **From:** `hello@mail.useboom.ai`

Let it through your spam filtering and make sure your rule also copies it to
Boom. If two checks in a row don't come back, Boom marks the support address
**Stopped** and emails your organization's admins. Users can filter it out of
their own inbox after it has been copied.

### What Boom does with the copies

* Email that carries a virus is dropped. Email flagged as spam is dropped
  too, unless the sender's domain proves it's real (DMARC): then it shows
  labelled **Marked as spam** for a person to judge.
* Email whose sender Boom can't verify (SPF, DKIM, DMARC) shows in the inbox
  labelled **Unverified sender**, but no automation acts on it.
* AI-written replies are drafts a person approves; nothing is sent by itself.

Details: [Email data & security](https://docs.useboom.ai/email-data-security.md).

## How to undo everything

* **Stop the copy:** delete the routing rule, mail flow rule or Gmail filter
  and forwarding address. Boom stops receiving immediately. Its daily check
  will then fail: after two misses the status shows **Stopped** and your
  admins get one email. To remove the support address from Boom so the checks
  stop, contact Boom.
* **Stop sending as your domain:** delete the DNS records Boom listed. Your
  main email is not affected. Emails Boom sends for your domain will then fail
  inbox checks, so ask Boom to remove the domain first: a domain that isn't
  verified yet can be removed with **Change domain**; a verified one is
  removed by Boom.
* **Undo a domain claim:** deleting the claim record does not move the domain
  back. To send from the other account again, add the domain there again.
* **Turn receiving off for your workspace:** an organization admin opens
  **Settings › Email › Advanced settings › Turn off receiving**. New emails
  from Boom then go out without a Boom reply address; replies to emails already
  sent, and mail to the Boom address, still arrive in the inbox. Remove the
  forwarding rule too if your support address should stop copying mail to
  Boom. **Turn on replies** brings it back with the same settings.

## Related

> [card] [Connect your support address](https://docs.useboom.ai/email-support-address.md)
>
> Step-by-step for each provider.

> [card] [Email data & security](https://docs.useboom.ai/email-data-security.md)
>
> Processing, retention, erasure and subprocessors.

> [card] [Email troubleshooting](https://docs.useboom.ai/email-troubleshooting.md)
>
> When something doesn't arrive.

> [card] [Email in Boom](https://docs.useboom.ai/email-replies.md)
>
> The whole guide: replies, support address and your domain.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.