Emails Missing From Business Domain — what to check first (MX, mail flow, quarantine, routing)
Steve H.
Expert ★★★★★ 27,853 satisfied customers
Specialities: business email delivery triage, missing inbound email diagnosis, MX/DNS validation, Microsoft 365 & Google Workspace mail flow checks.
When emails go missing on a business domain, start with mail flow evidence: MX/DNS, quarantine, routing rules, and sender bounce codes before changing settings
Technician
We’ll keep this safe: no deleting rules blindly, no turning off security, and no “big changes” until we have evidence.
To narrow it down, tell me:
1) Which platform hosts your email (Microsoft 365/Exchange Online, Google Workspace/Gmail, something else)?
2) Is it all senders or only specific senders/domains (banks, vendors, website forms)?
3) Did this start after any change (DNS update, domain move, new spam filter, new connector, website migration)?
Technician
First trust moment: I don’t want you to start toggling random “anti-spam” switches or deleting rules, because that can hide the real cause and create compliance problems later.
Quick, low-risk questions:
1) Are you missing inbound emails only, or outbound too?
2) When a client “sends,” do they get a bounce/NDR (an error like 5.1.1, 4.7.x), or do they see “delivered”?
3) Are all mailboxes affected, or just one person (for example, only accounting@ or only your mailbox)?
Technician
Safe check #1 (no changes): ask one client to forward you the bounce message (NDR) or at least the error code and timestamp. Those details tell us whether the issue is DNS/MX, recipient resolution, anti-spam rejection, or rate limiting.
Safe check #2: have you recently changed anything related to the domain — registrar, DNS provider (Cloudflare), MX records, or added a third-party email security gateway?
Technician
Trust moment #2: I don’t want you to “fix” this by changing five things at once. We’ll isolate one variable at a time, because that’s how you avoid making deliverability worse.
Questions (different order intentionally):
1) In Microsoft 365 admin, do you use connectors or mail flow rules for that security product?
2) Are you missing emails from outside senders only, or also internal (user-to-user within your domain)?
3) Are any missing messages later found in quarantine or the junk folder?
Technician
Safe checks you can do without “breaking” anything:
• MX verification: confirm your public MX records point where you think they do (to Microsoft 365, or to the security gateway if that’s the design). A wrong or mixed MX is one of the top causes of “emails never arrive.”
• Connector logic: if you configured a rule like “only accept inbound mail from the security gateway,” then direct-to-M365 mail can be rejected or dropped when senders bypass the gateway.
• Quarantine scope: some products quarantine before Microsoft 365 sees the message, meaning it won’t appear in Microsoft quarantine at all.
Technician
Safe check sequence (diagnostic, not a full fix):
1) Get one concrete example: a sender address + recipient + timestamp + whether they got a bounce.
2) Run a message trace in Microsoft 365 for that timestamp/recipient. If there’s no trace at all, the message likely never reached Microsoft 365 (DNS/MX/gateway path). If trace exists, then it’s filtering, routing, or mailbox rules.
3) Check the security product’s inbound logs/quarantine for the same sender/time window.
Trust moment #3: I don’t want you to disable forwarding rules yet — first we prove whether mail is arriving and where it stops.
Technician
Here’s how to separate it safely:
• If message trace shows “Delivered” but users don’t see it, then it’s mailbox-side: rules, focused/other tabs, junk, or a shared mailbox permission/routing issue.
• If message trace shows “Quarantined/Filtered”, it’s security policy or spam filtering.
• If there’s no trace, it’s upstream: MX/DNS, connectors, gateway, or sender-side blocks/bounces.
Firewall changes can matter only if you host your own mail server (most Microsoft 365 setups do not).
Technician
Two quick, safe checks (no policy changes required):
1) Confirm MX records are only what you intend (no leftovers pointing to old providers). Mixed MX can lead to “some senders deliver, some don’t.”
2) For vendors reporting issues, ask them for the exact SMTP error they receive. Even one line like “550 5.7.1” tells us whether it’s a rejection, a routing failure, or a policy block.
Technician
The safest approach is evidence-first:
• If Microsoft trace is empty for missing emails, focus on DNS/MX and the gateway path (without touching records yet).
• If Microsoft trace shows delivery, focus on quarantine, transport rules, and mailbox rules (again, we review before removing).
• If the gateway has the messages, you adjust the gateway/connector logic, not your whole domain.
Once you have 2–3 examples with timestamps, we can pinpoint the failure point without “trial-and-error.”
Technician
Safe checks for the form case:
• Ask your web developer for the form provider’s sending domain/IP and whether they see bounces in their dashboard.
• Test delivery to a second address inside your domain (for example, send to two recipients). If one receives and one doesn’t, it’s mailbox/rules. If neither receives and there’s no trace, it’s domain routing/gateway.
• Confirm the form is sending to the correct address (typos and outdated aliases happen after mailbox changes).
You’re doing the right thing by treating this as a mail-flow investigation, not an Outlook “button problem.”
Quick answer: the accepted fix
Most “emails missing from a business domain” cases become clear once you confirm where the message stops.
• Start with evidence: collect 2–3 examples (sender, recipient, timestamp, any bounce/NDR text).
• Check mail flow logs: run a Microsoft 365 message trace; if there’s no trace, focus on MX/DNS and any inbound gateway path.
• Review filtering safely: check quarantine and mail flow rules/connectors before changing them.
• Isolate one variable: compare “direct to Microsoft 365” vs “through the security gateway” behavior using logs, not guesswork.
• Avoid risky changes: don’t disable security or delete rules until you’ve identified the exact failure point.
Common reasons business-domain emails go missing (and why it can start suddenly)
Sudden inbound email loss is often triggered by DNS/MX changes, a new email security gateway, or an updated connector / mail flow rule that changes what your tenant accepts. Another frequent cause is filtering: messages arrive but are held in quarantine, routed to the wrong mailbox, or rejected due to policy. Because different senders deliver differently, a mixed or incorrect MX setup can look random (“some clients get through, others don’t”). The fastest path is to trace one example end-to-end using timestamps and logs.
Safe checks before you change DNS, disable spam filtering, or “reset everything”
Start with reversible checks: confirm your public MX records match your intended design (Microsoft 365 vs gateway), and verify there are no leftover MX entries to old providers. Use message trace to learn whether the email reached Microsoft 365, and review quarantine and mail flow rules/connectors before you modify them. If a third-party gateway is involved, compare its inbound logs with Microsoft’s trace for the same timestamp. Avoid multiple simultaneous changes — in deliverability work, controlled testing prevents accidental downtime.
Security tip: don’t “fix” missing email by lowering protections
Business email issues often attract risky advice.
If someone suggests turning off spam filtering, disabling connectors, or removing security policies “just to test,” pause first. Those actions can expose your domain to phishing, spoofing, and business email compromise attempts. A safer approach is evidence-based: verify MX/DNS, check quarantine, and compare gateway logs with Microsoft 365 message trace. Keep a short incident note (what changed, when it started, which senders are affected) so you can troubleshoot without losing control.
Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by provider, tenant policies, and DNS host. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.
Getting Started Is Easy
Evidence-first diagnosis
Confirm whether inbound mail reaches your tenant, gets filtered, or never arrives due to MX/DNS or gateway routing.
Low-risk checks
Use safe reviews (message trace, quarantine, connector logic) before making changes that could cause downtime.
Escalation-ready notes
Capture sender, timestamp, and bounce codes so IT or vendor support can pinpoint the failure point faster.
FAQ
Why did it start suddenly?
Sudden missing inbound email usually follows a change: DNS/MX updates, a new email security gateway, or a connector/mail flow rule update. Some senders may still target old MX entries if records are mixed. Filtering can also shift after policy updates, placing mail into quarantine instead of the inbox. Start by tracing one real example using timestamps and any bounce/NDR text.
Did this happen after an update (DNS, security, or Microsoft 365 changes)?
Yes, updates can change what your domain accepts and how it routes inbound mail. A gateway “only accept from X” rule can reject mail that arrives directly to Microsoft 365. DNS propagation and cached MX results can make the issue look inconsistent between senders. Use message trace and gateway logs to confirm the actual path before changing settings.
Is it hardware or settings?
If multiple users miss inbound mail, it’s rarely a laptop, router, or Outlook setting. Delivery happens server-to-server first, so logs are the quickest truth source. If message trace shows delivery but users can’t find it, then mailbox rules or spam/junk behavior is likely. If there is no trace, focus on MX/DNS and inbound routing or gateway handling.
Can this be fixed without service?
Often you can identify the cause with safe checks: validate MX records, review quarantine, and run message trace for a known missing email. Many issues are configuration mismatches rather than “broken email.” However, if a gateway/connector design is involved, it may require a careful admin change to avoid downtime. Don’t make broad changes until you know exactly where messages stop.
Sources
- Microsoft Learn — Find and fix email delivery issues (Microsoft 365 admin)
- Microsoft Learn — Troubleshoot mail flow in Exchange Online
- Google Workspace Admin Help — Troubleshoot problems receiving emails in Gmail
- Cloudflare Docs — Troubleshooting email issues (DNS/MX)
Filed under: Account Access Help
Related articles
- Emails Missing After Domain Change — what to check first (DNS, MX, routing) without breaking mail flow
- Emails Missing From Clients Suddenly — what to check first (before you change anything)
- Emails Missing From Admin Account — what to check first (without losing anything)
- My emails are missing, but there’s no error — where did they go?
- Emails missing only from certain senders — where did they go?
- Emails Missing From Our Work Domain — what to check first (without breaking mail)
- Emails Missing from Shared Inbox? How to Restore Access Fast
- Emails Missing From Microsoft 365 — not in Inbox, Search, or folders (what to check first)
