> ## 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 troubleshooting

> Fixes for the common email problems: nothing arriving, replies going somewhere else, Microsoft 365 blocking forwarding, Gmail's confirmation, and the daily check email.

Start in **Settings › Email**. Under **Reply to customers from Boom**, the
**Replies to your emails** and **Support address** rows
show where replies go right now and how your support address is doing; most
answers start there.

## I'm not receiving email

**Replies to your emails don't show up.**

* Check that the **Replies to your emails** row shows **Working**. If you see
  **Turn on replies**, receiving isn't on yet: an organization admin clicks it
  (it unlocks once sending shows **Ready**: a verified domain and a sender).
* Check the email had no Reply-To of its own. A template or journey step with
  its own Reply-To sends replies there, not to Boom.
* Clear your inbox filters. A reply from a sender Boom can't verify does
  arrive, labelled **Unverified sender**, but it gets no AI draft and doesn't
  move journeys.
* Email flagged as a virus, or as spam from a domain that doesn't pass DMARC,
  is dropped. Archives, programs, HTML and SVG attachments are skipped, not
  stored.

**Emails to your support address don't show up.** Look at the status on the
**Support address** row:

| Status | What to do |
| - | - |
| **Connect** button, no status | Click **Connect** and follow [Connect your support address](https://docs.useboom.ai/email-support-address.md). |
| **Waiting for the first email** | Boom sends a check email within the hour. If it's been longer, check the rule exists and points at your Boom address (copy it from the row, or from **Advanced settings**). With Gmail, open the confirmation link first ([below](#gmail-confirmation-never-arrived)). |
| **Stopped** | The copy stopped reaching Boom. Check that the rule still exists in your email provider and doesn't send mail to spam. Replies go to Boom's address meanwhile, so nothing is lost. |
| **Stopped**, "Boom's check email never came through" | The check never came back in its first week, so Boom stopped sending it. Check the address and the steps, then save the address again to restart the checks. |

Click **Send test** on the **Support address** row to check the copy right
away instead of waiting for the next daily check. If it says **Didn't arrive
yet. Check:** after 90 seconds, it lists what to check for your provider. A new Google
Workspace or Microsoft 365 rule can take up to an hour to start working, and
Boom keeps checking in the meantime. If it says to wait a minute, a check
email just went out: you can send one test a minute.

If your rule only copies some emails (a Gmail filter, a mail flow rule with
conditions), make sure it also matches the check email: subject
`Boom forwarding check`, from `hello@mail.useboom.ai`.

## Replies go to the wrong place

Open the **Replies to your emails** row. It says where customers' replies go right now:

* **"Replies go to [support@yourcompany.com](mailto:support@yourcompany.com)"**: **Replies go to your support
  address** is on under **Advanced settings**, and your support address is
  connected with its daily check passing. Replies reach your own inbox and
  Boom.
* **"Replies go to Boom"**: the default, a private Boom address per
  conversation. Replies reach Boom only, not your own inbox.

The line changes on its own: if one daily check doesn't come back, replies
switch to the private Boom address so nothing is lost while the copy is
broken, and switch back once a check comes through again. So if you expected
your support address and see the Boom address, check that the switch under
**Advanced settings** is on, then look at the support address status above.

A template or journey email step with its own **Reply-To** wins over both.
If replies to one campaign go somewhere else, check that step's Reply-To.

## Microsoft 365 blocks forwarding

Microsoft 365 blocks automatic forwarding to outside addresses by default.
Forwarding from a mailbox or with an Outlook rule bounces unless an admin
allows it in the outbound spam policy (**Microsoft Defender → Anti-spam
policies**).

Use the recipe in [Connect your support address](https://docs.useboom.ai/email-support-address.md#microsoft-365)
instead: an Exchange mail flow rule that adds your Boom address as **Bcc**. It
needs a Microsoft 365 admin.

## Gmail confirmation never arrived

When you add your Boom address as a forwarding address, Gmail sends its
confirmation email to Boom, not to your inbox. It shows in the **Support
address** row in **Settings › Email**, under the Gmail steps: **Waiting for
Gmail's confirmation…** and then **Open confirmation link**, without
reloading.

* **Only organization admins see the link.** Others see "An admin needs to
  open Gmail's link here."
* **Check the address.** The address you saved in Boom must be the Gmail
  address you're forwarding from, and the forwarding address in Gmail must be
  your Boom address exactly.
* **The link expires.** If Boom says "Gmail's link expired", add
  the Boom address in Gmail again to get a new one.
* **Google Workspace routing needs no confirmation.** If you used the
  [Google Workspace steps](https://docs.useboom.ai/email-support-address.md#google-workspace), skip this.

## Daily check email in my inbox

Once a day Boom sends an email titled **Boom forwarding check** (from
`hello@mail.useboom.ai`) to your support address. When it comes back through
your rule, Boom knows the copy still works. It's how Boom notices a broken
rule and switches replies back to its own address before anything is lost.

You can hide it from your own inbox: create a filter on that subject that
skips the inbox or archives it, as long as your copy rule still sends it to
Boom. Don't block or delete it before the copy happens, or the status will
show **Stopped**.

## My domain stays pending

Open **Settings › Email**, **Your domain**: each record shows **Found** or
**Not found yet** (or, with the `boom1._domainkey` records, **Found,
confirming…** for a
record already in your DNS that is still being confirmed, and **Covered by**
your root domain for a DMARC policy you already have).

* **Records not found after a day:** check each name and value against Boom,
  character by character. Many DNS hosts add your domain to the name
  automatically, so `boom1._domainkey.yourcompany.com` typed in full becomes
  `boom1._domainkey.yourcompany.com.yourcompany.com`. Enter the name exactly as
  Boom shows it.
* **CNAME records not found on Cloudflare:** Cloudflare can **proxy** a
  record (orange cloud). A proxied CNAME answers with Cloudflare's own
  addresses instead of pointing where Boom asked, so Boom reads it as **Not
  found yet** and inboxes can't check your DKIM signature. In Cloudflare, open
  each CNAME Boom lists (the `boom1._domainkey` and `boom2._domainkey`
  records), set **Proxy status** to **DNS only** (grey cloud), save, then
  click **Check now**. Other DNS hosts with a proxy or "CDN" switch need the
  same: the email records must not go through it.
* **Still not found after 72 hours:** checks for the `boom1._domainkey`
  record stop then. Fix the record, then click **Check now**: Boom starts a
  new 72-hour window. The name and value stay the same.
* **Signing found, `send` records pending:** Boom waits for the `send` MX and
  SPF records before it sends anything, so nothing bounces meanwhile. Add
  both. See [Email setup for your IT team](https://docs.useboom.ai/email-for-it.md).

## My domain says "needs attention"

Boom checks your verified domain with your email provider every day. If a
record that used to be found stops verifying (usually after someone edits or
removes it in your DNS), **Settings › Email** shows **needs attention** on your
domain with a warning above the records. Boom keeps sending from the domain,
but inboxes may reject those emails or put them in spam until the records are
back.

Open **Your domain**, restore each record marked **Not found yet** exactly as Boom
shows it, then click **Check again**. The warning goes away once the records are
found again. If someone else manages your DNS, send them
[Email setup for your IT team](https://docs.useboom.ai/email-for-it.md).

## Emails bounce or land in spam

See [Email deliverability](https://docs.useboom.ai/email-deliverability.md): what each delivery result
means, which addresses Boom stops emailing and how they come off, and what
Gmail, Yahoo and Microsoft require from bulk senders.

## Related

> [card] [Email deliverability](https://docs.useboom.ai/email-deliverability.md)
>
> Bounces, spam reports, and the undeliverable list.

> [card] [Email in Boom](https://docs.useboom.ai/email-replies.md)
>
> Your domain and senders, replies and support address, and what each status means.

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

> [card] [Email setup for your IT team](https://docs.useboom.ai/email-for-it.md)
>
> What to add and how to undo it.

> [card] [Email data & security](https://docs.useboom.ai/email-data-security.md)
>
> Where email is processed and how long it's kept.


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