Technician helping troubleshoot Fire TV automation and Alexa routine issues for seniors

Steve H.

Reviewed for technical accuracy

Specialities: work email delivery diagnostics, Google Workspace & Microsoft 365 mail flow triage, DNS/MX/SPF sanity checks, quarantine & routing rule review.

When business email doesn’t arrive, start with the safest checks: domain DNS/MX health, admin quarantine, routing rules, and mailbox filters—before changing anything

Technician avatar Technician
Hi! When emails “go missing” for a company domain, it’s usually one of three buckets: they never reached your mail system, they were accepted but diverted (quarantine/rules), or they’re present but not visible (filters, focused inbox, client sync).

I don’t want you to change DNS or security settings yet — that can make a small issue bigger. Let’s start with the safest checks and narrow it down.

First, which setup are you using: Google Workspace, Microsoft 365/Exchange, or a hosted provider? And is the problem: all senders, or just specific senders/domains?
Customer
Microsoft 365. It’s not all email, but several clients say they’ve sent invoices and we don’t see them. It started this week. Internal email works.
Technician avatar Technician
Good detail: internal mail working suggests your tenant and mailboxes are generally OK. Since it’s some external senders, we should check for: message rejection (NDR on sender side), anti-spam quarantine, transport rules, and “accepted but moved” behavior.

Quick clarifier (different angle first): did anything change this week — a DNS update, new security product, migration step, new connector, or a change to your domain registrar?
Customer
We moved DNS to Cloudflare last weekend. We tried to copy the records carefully. Mail seemed fine at first, then these missing messages reports started coming in.
Technician avatar Technician
That’s a very common timeline. DNS moves can create “partial delivery” symptoms if an MX record is slightly off, if a legacy MX is still present, or if different senders are hitting different MX endpoints during propagation/caching.

Trust moment: I’m not going to tell you to delete records on the spot. We’ll just compare what’s published vs what Microsoft 365 expects.

Safest checks first:
1) Do you have one MX record for the domain, pointing to Microsoft 365 (highest priority), with no old provider MX left behind?
2) Are the missing messages for all recipients, or just one mailbox/user?
3) When a client says they sent it, can they provide an NDR/bounce or “delivered” confirmation?
Customer
I think we have one MX, but I’m not fully sure. It’s affecting two people more than others. One client got a bounce about “couldn’t deliver,” but another says it sent successfully with no error.
Technician avatar Technician
Two different sender outcomes usually means two different paths:
• Bounce/NDR: the sender’s server tried and got a rejection or couldn’t find the right destination.
• “Sent successfully”: the sender believes it handed off the message, but it may have been filtered, quarantined, or routed elsewhere on receipt.

Let’s isolate where the mail disappears — without making changes.

First low-risk test: for one “missing” subject line, can you check whether it’s in any of these places?
• Junk/Spam
• Deleted Items
• Archive
• Other/Focused inbox tabs
• Mail rules (a rule that moves invoices/attachments)
Customer
We checked Junk and Deleted. Nothing. One of the users has a bunch of rules from years ago. Also we use Outlook desktop and sometimes it doesn’t sync instantly.
Technician avatar Technician
Those are both strong suspects, and they’re safe to check.

Another trust moment: I don’t want you to delete rules or reinstall Outlook right now. Let’s prove whether this is a client-view issue or a server-side delivery issue.

Safe comparison check:
1) Look for the same message in Outlook on the web (browser) for that mailbox. If it shows up there but not in Outlook desktop, that’s a sync/cache view problem.
2) If it’s missing in both places, we treat it as mail flow (filtering/routing/DNS).

While you do that, do you have any security products in front of Microsoft 365 (a gateway, journaling, or a third-party filter)?
Customer
No third-party gateway. Outlook on the web also doesn’t show the missing invoice email. That’s why it feels scary. We do have anti-phishing policies and some quarantine settings.
Technician avatar Technician
If it’s not in webmail, we’re right to focus on delivery and filtering.

Here’s a safe way to reason about it:
• If the sender got an NDR → it’s often DNS/MX/recipient/transport-level rejection, and the evidence is in the bounce text.
• If the sender did NOT get an NDR → it may have been accepted and then quarantined or routed away, and admin tools can usually trace it.

For the client who got a bounce, what does it mention — “recipient not found,” “domain not found,” “550,” or “temporarily unable”? Even one line helps.
Customer
They forwarded a screenshot: “550 5.1.1 The email account that you tried to reach does not exist.” But the mailbox does exist and is active.
Technician avatar Technician
A 5.1.1 can happen even when the mailbox exists if the sender is reaching the wrong destination (old MX), if there’s a mismatch like an alias vs primary address, or if the sender cached an outdated route.

Safe checks that don’t change settings:
1) Confirm the exact recipient address the client used (typos, old domain variant, missing alias).
2) Check whether the mailbox has the expected proxy addresses/aliases (for example: firstname.lastname@ vs first.last@).
3) Verify the domain has only the intended MX pointing to Microsoft 365 — no leftover records that could capture mail elsewhere.

Separate question: are the missing invoices from a single vendor system (like a billing platform), or from multiple unrelated senders?
Customer
Mostly one vendor (an invoicing app), but a couple were from regular clients too. The vendor uses automated emails.
Technician avatar Technician
Automated senders are more likely to hit filtering policies (attachments, links, spoofing signals) and can land in quarantine without an obvious user-visible trace.

Third trust moment: don’t loosen security policies broadly “just to test.” Instead, do targeted observation:
• Check admin quarantine for the timeframe and the sender domain/address.
• If you have a message trace tool, look up that sender and recipient to see whether the message was received, quarantined, rejected, or redirected.

Also, after your DNS move, do you know if your Autodiscover or other records changed? Sometimes people copy an old record set and mail-related entries don’t match the tenant.
Customer
We copied the records from the old provider. I’m not sure about Autodiscover. We did see some quarantined messages last month, but I haven’t checked this week yet. We can check message trace.
Technician avatar Technician
Perfect. If message trace shows “never arrived,” we look at DNS/MX and sender-side evidence (NDRs). If it shows “arrived then quarantined/redirected,” we focus on policies and rules.

Two safe pitfalls to watch for while you investigate:
1) Forwarding (user-level or admin-level) can silently send mail elsewhere, especially if it was set years ago.
2) A transport rule can redirect or block messages with certain subjects like “invoice,” attachments, or links.

Last quick question: do the affected users share something in common (same group, same shared mailbox, same rules template), or is it random?
Customer
They’re both in the finance group and have similar mailbox rules. One is also a shared mailbox. That might explain why it’s concentrated.
Technician avatar Technician
That’s a solid lead and it’s the kind of “looks like a domain problem” issue that turns out to be policy + rules + mailbox type.

Safe next steps (still diagnostic): compare one missing sender in message trace for a normal user vs the shared mailbox; check quarantine for that sender/timeframe; and review finance rules for moves/redirects. If you can capture one NDR example and one “sent successfully” example, you’ll have enough evidence to pinpoint whether it’s DNS routing, filtering, or a mailbox-level rule — without making risky changes.

Quick answer: the accepted fix

Accepted first step when emails are missing from a work domain: 1) confirm whether the message exists in webmail (rules out desktop sync/view issues), 2) check admin quarantine and run a message trace for one example sender/recipient/time, 3) validate that the domain’s MX points only to the current mail provider (no legacy MX), 4) review shared mailbox and finance mail rules/forwarding for redirects or silent moves, and 5) collect one bounce/NDR example (if any) plus the exact recipient address used. These steps are safe, reversible, and help you identify whether this is routing, filtering, or mailbox behavior before any changes.


Common reasons business emails “disappear” after a DNS or domain change

Mail delivery depends on DNS routing and policy checks. After a DNS move, some senders may still use cached routes, a legacy MX record can capture mail at an old provider, or a typo/alias mismatch can trigger a sender-side bounce. In other cases the message is accepted but diverted by quarantine, transport rules, or forwarding—so it never appears in the inbox even though the sender sees “sent.”

What to check first (safe checks before you touch DNS or security policies)

Start with comparisons that don’t change your setup: verify the message isn’t simply hidden by client sync, Focused inbox, or a rule; check admin quarantine for the sender and timeframe; run one trace to learn whether the message was received, rejected, or redirected; and confirm there’s only one intended MX route to your current provider. Avoid broad security relaxations during testing—use evidence (trace results, quarantine hits, NDR text) to decide what actually needs attention.

Safety tip: don’t “fix” email by guessing—keep tests controlled

Small changes to DNS and policies can have big side effects.

If you’re missing important mail, avoid changing multiple things at once (MX + rules + security) because it becomes hard to know what helped—or what broke something else. Use one or two controlled checks (webmail vs desktop, quarantine/trace for a single example, MX sanity check) and write down results with timestamps. That evidence makes it much easier to correct the real cause without weakening protection or disrupting delivery.

Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by device, region, and service. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.

Understand what these prompts mean


Getting Started Is Easy

Low-risk triage

Determine whether missing mail is routing (MX/DNS), filtering (quarantine/policies), or mailbox rules/client view.

Evidence-based checks

Use a single example message to check quarantine/trace outcomes without changing DNS or weakening protection.

Admin-ready notes

Capture NDR text, sender/recipient, and timestamps so the right team can resolve it efficiently.

FAQ

Why did emails stop arriving after we moved DNS for our domain?

A DNS move can expose MX mismatches, leftover legacy MX records, or caching differences across senders. Sometimes mail is delivered to an old provider or rejected due to an address/alias mismatch. Checking MX and running a trace on one example is the safest way to confirm the path.

How can I tell if the message was quarantined instead of delivered?

If users can’t see it in webmail, check the admin quarantine and message trace for the sender and timeframe. Quarantine can hold messages without showing up in the inbox. Trace results usually indicate “quarantined,” “delivered,” “redirected,” or “failed.”

Could Outlook rules or a shared mailbox make emails look “missing”?

Yes. Rules can move or delete messages, and shared mailboxes can have different policies or routing. Comparing Outlook desktop vs Outlook on the web helps rule out sync/view issues. Reviewing forwarding and rules for affected users is a safe diagnostic step.

What should I collect before I ask a sender to resend an invoice?

Ask for the exact recipient address used, the send time, and any bounce/NDR text or delivery confirmation. If they received an NDR, even a screenshot helps. With that, you can match it to trace results and avoid guesswork.

Sources

Filed under: Account Access Help

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant