How to Check if Outlook Is Auto-Rejecting Your Email: Complete Diagnostic Guide

Short answer: "Rejected" is actually four different outcomes wearing one name - a hard bounce back to the sender, a silent drop with nothing to see anywhere, an automatic forward or copy to somewhere else, or a delivery that succeeded and then got filed into Junk or quarantine. Each leaves different evidence, and only one tool - message trace - gives you the receiving server's own record instead of a guess built from symptoms.

• If you're the recipient and one sender's mail never shows up: start with your own inbox rules and blocked senders list before assuming anything about the sender.
• If several people on your domain have the same problem with the same sender: the cause sits at the tenant level, not in anyone's personal mailbox.
• If you have admin rights on the mailbox in question: message trace answers this in minutes instead of hours of checking settings one at a time.
• If you don't have admin rights: you can still clear every personal-mailbox cause yourself, then hand a short, specific list to whoever does.

The Four Outcomes Behind "Rejected"

"How do I check if my email is auto-rejecting in Outlook" is really four separate questions wearing a single sentence, and the answer depends entirely on which one you're actually asking. A message can be refused outright during delivery, which produces a bounce the sender can read. It can be accepted and then quietly discarded, which produces nothing at all - no bounce, no trace in any folder a normal search reaches. It can be accepted and automatically forwarded or copied somewhere else by a rule nobody remembers writing. Or it can be accepted, filed into Junk or a quarantine queue, and simply never surface where anyone is looking.

These are not shades of the same problem. They have different causes, live in different settings, and are fixed by different people. Treating all four as "my email is being rejected" is exactly how people spend a week adjusting spam filters when the real cause was a three-year-old inbox rule, or the other way around.

This guide is written for the side of the conversation that can actually go look: the mailbox owner or the admin of the Microsoft 365 tenant in question, checking whether their own Outlook setup is the reason mail isn't arriving. If you're on the other side of that - a sender staring at a bounce with no access to the recipient's mailbox at all - the diagnostic path is different and is covered in full in Outlook blocking your emails. If you already know a bounce came back with a specific code, that guide's error-code table is the faster route. This one is for when you can open the settings yourself and want a systematic way to actually find the answer instead of guessing. The wider set of delivery diagnostics sits in our guides library.

Start Here: What Kind of Mailbox Is This

The tools available to you depend entirely on what kind of Outlook account is involved, and checking this first saves you from hunting for settings that don't exist for your account type.

If you're on a company domain and you are not the admin, the second column is not wasted effort. Ruling out your own mailbox first is exactly what turns "can you check why my emails aren't arriving" into a specific, answerable request instead of a vague one. Admins move much faster when you can tell them it isn't your rules, your blocked senders list, or your junk settings before you ask them to look at anything tenant-wide.

Check Your Own Inbox Rules First

Inbox rules are the single most common cause of mail that seems to vanish, and they are also the most commonly skipped check, because most people assume a rule they don't remember writing can't be the problem. It usually is.

Where to find them depends on which Outlook you're in: Outlook.com and Outlook on the web keep rules under Settings, then Mail, then Rules. Classic desktop Outlook keeps them under File, then Manage Rules and Alerts. The newer unified Outlook app keeps them under Settings, then Mail, then Rules as well, though the exact wording shifts a little between versions. If you use more than one client, check all of them - rules created years ago in desktop Outlook are still active even if you've switched to the web client since.

Read every rule, not just the ones with obvious names. What to look for:

• Actions that remove mail from view. Move to a folder other than Inbox, mark as read, delete, or permanently delete. Any of these makes mail disappear without a trace unless you know to look in that specific folder.
• Conditions that are broader than they look. A rule filtering on a keyword, a domain, or "from certain people" can catch mail nobody intended it to catch, especially once a sender changes their display name or starts sending from a new address at the same domain.
• The "stop processing more rules" checkbox. Rules run in order, and a rule earlier in the list with this option enabled prevents every rule below it from ever running - including a rule you added later specifically to fix the problem you're troubleshooting.
• Rules you don't remember creating. Shared mailbox delegation, a colleague helping "clean up" your inbox, or an old automation tool can all leave rules behind that nobody currently using the mailbox is aware of.

One more mechanism worth naming separately: automatic forwarding. A rule - or a mailbox-level forwarding setting, sometimes called SMTP forwarding - that silently forwards mail to another address means you never see it fail; it just goes somewhere else. If you suspect this, check both the rules list and, separately, your account's forwarding setting, since Outlook treats them as two different features even though the visible effect looks identical from outside.

Blocked Senders, Safe Senders, and Strict Junk Settings

Junk email settings sit in a different place from rules and cause a different flavor of the same symptom.

Blocked senders

Anything on your Blocked Senders list is discarded or sent straight to Junk depending on your settings, and addresses land here more often by accident than by intent - a single misclick on "Block sender" from the wrong message, or a colleague blocking an address for a completely different reason, is enough. Check the list directly rather than trusting your memory of what's on it.

Safe senders

The inverse list, and useful in the other direction: adding a sender here is the fastest way to stop them being filtered again while you investigate the underlying cause.

The strict junk mode most people don't know exists

Outlook's junk email options include a setting along the lines of "Only trust email from my Safe senders and Safe recipients lists." Turned on, this treats every sender not explicitly on your safe list as junk, regardless of their actual reputation or content. It is easy to enable by accident while adjusting other junk settings, and it is one of the more dramatic causes of "everything from everyone except a handful of people is being rejected" - because, functionally, that is exactly what it does.

All three of these settings exist per mailbox on Outlook.com and in Microsoft 365, and per profile in desktop Outlook, so check them in whichever client the affected mailbox actually uses day to day.

Tenant Mail Flow Rules That Reject or Redirect

This is where the investigation moves from your mailbox to your organization, and it's the first tenant-level tool worth checking because a mail flow rule - also called a transport rule - can produce every one of the four outcomes from the introduction, deliberately, by design, for a whole domain or a narrow slice of it.

An admin manages these in the Exchange admin center at admin.exchange.microsoft.com, under Mail flow, then Rules. Each rule has a condition (who it applies to, what it matches) and an action, and the action is what determines which outcome you get:

Rules are commonly scoped narrowly - to a specific sender domain, a keyword in the subject, or a specific recipient - which is exactly why one sender's mail can vanish while everyone else's arrives normally, or why one person on a domain has a problem their colleagues don't. If you have admin access, scan the rules list for anything referencing the sender's domain, an unusual keyword, or a rule with no obvious business purpose. Rules are also frequently created for a reason that made sense at the time - blocking a specific spam campaign, redirecting mail during someone's leave - and then never removed once that reason expired.

The Tenant Allow/Block List

Separate from mail flow rules, the Tenant Allow/Block List is where an admin explicitly blocks, or allows, specific senders, domains, URLs, or files, and it's a fast, common way for a single sender or domain to start being rejected without anyone changing a general policy.

An admin manages entries in the Microsoft Defender portal, under Email & collaboration, then Policies & rules, then Threat policies, then the Tenant Allow/Block Lists page - or directly at security.microsoft.com/tenantAllowBlockList. Mail from a blocked entry is treated as high confidence spam, and entries typically become active within minutes of being added, so a rejection that started suddenly, with no other change, is worth checking here first, since it points to a recent, deliberate action rather than a gradual reputation problem.

One detail catches people out: blocking a domain or address here is two-way in effect. Not only does mail from that domain get treated as spam coming in, but your organization's own users are also prevented from sending to that domain or address. If someone on your team can no longer email a specific external contact either, and that contact's mail into your organization has also gone quiet, a block-list entry covering their domain is a very likely explanation, and a quick one to confirm.

Anti-Spam Policies and Connection Filtering

If nothing so far explains it, the next layer is the tenant's general spam filtering configuration, which is broader and less obviously tied to one sender than a rule or a block-list entry.

Anti-spam inbound policies, in the Defender portal at security.microsoft.com/antispam, set thresholds for how aggressively incoming mail is scored and what happens at each verdict - move to Junk, quarantine, or another action, depending on how confident the system is that a message is spam or bulk mail. A policy tuned more aggressively than the default will catch mail a less strict tenant would let through, and this is tenant-wide or scoped to specific users and groups, not something one mailbox owner controls.

Connection filtering is a separate, earlier check: its own IP Allow/Block list operates before message content is even evaluated. A sending IP on the block list is refused at the connection level - the content of the message is irrelevant, because the conversation never gets that far. This is worth knowing because it means "the content was fine, so it must not be a filtering issue" isn't a safe conclusion; connection filtering doesn't look at content at all.

Both of these are firmly admin-only territory. If you've ruled out your own rules, your own junk settings, tenant mail flow rules, and the Tenant Allow/Block List, and the problem persists, this is the specific, narrow thing to ask your admin to check next, rather than a general "can you look into why emails aren't arriving."

Quarantine: Held, Not Rejected

Quarantine deserves its own explanation because it produces the exact symptom set that makes people conclude a message was rejected, when it actually wasn't - it was accepted and held.

A quarantined message exists, is retained, and sits in a queue that no ordinary mailbox search reaches, because it never made it into the mailbox at all. Whether the intended recipient is even told they have something waiting depends on the organization's quarantine policy - notification is common but not universal, and plenty of organizations run with it effectively off for certain categories of mail. That is precisely why "no bounce, not in Inbox, not in Junk" so often turns out to be quarantine that nobody happened to mention.

An admin can search and release quarantined messages in the Defender portal at security.microsoft.com/quarantine. Depending on the quarantine policy's configured permissions, some end users can see and release their own quarantined mail directly too - worth checking, since it may resolve the immediate problem without waiting on IT at all.

Message Trace: The Definitive Tool

Everything above is a checklist of places a problem could be hiding. Message trace is different - it's the receiving system's own record of what actually happened to a specific message, and it ends the guessing.

Find it in the Microsoft Defender portal under Email & collaboration, then Exchange message trace, which passes through to the newer Exchange admin center's message trace page directly at admin.exchange.microsoft.com/#/messagetrace. Running one requires permissions - membership in the Organization Management, Compliance Management, or Help Desk role group, or the Global Administrator or Compliance Administrator role - so this is squarely an admin, or delegated help desk, tool rather than something every mailbox owner can run themselves.

To run a trace, enter the sender and recipient addresses and a date range, then choose a report type. The default Summary report has the smallest row limit and shortest lookback; if a message doesn't show up there, switch to Enhanced summary or Extended before concluding it isn't findable - a narrower report type missing a message is a common false negative, not proof the message never arrived.

What you get back tells you whether the message was received, rejected, deferred, or delivered by the service, along with the sequence of actions taken on it before it reached that final status - including actions like a mail flow rule firing, or a quarantine verdict being applied, that are otherwise invisible from outside the tenant.

How to Read What Message Trace Tells You

A trace result is only useful once you know how to read it against everything else you've already checked.

• Status shows delivered, but the recipient insists nothing arrived. The message reached the mailbox. The cause is downstream of delivery - almost always a personal inbox rule, a forward, or the message sitting unnoticed in Junk. Go back to the personal-mailbox checks above rather than anything tenant-level.
• Status shows a rejection, with a specific rule referenced in the detail. You've found it. That mail flow rule is the direct cause - open it, and either narrow its condition or add an exception for the sender in question.
• Status shows quarantined. Go to the quarantine section above - the message is sitting there, not gone.
• Status shows pending or failed, with no rule or policy referenced. This points toward a genuine delivery problem rather than a deliberate filtering decision - a different, narrower investigation than anything on this page, and closer to the territory covered in emails not being delivered.

Once you know the true cause, resist the urge to just switch it off. Ask why it existed in the first place - a rule or block-list entry is sometimes there for a good reason that happens to be catching an exception it shouldn't. Make the narrowest fix that solves the specific case, such as an exception for one sender rather than disabling a rule that protects everyone else, then send a real test message afterward and confirm it lands, rather than assuming the settings change alone is proof.

If the tenant-level tools come back clean on every count above and a specific external sender is still being refused, the direction of the investigation flips outward: work through Outlook blocking your emails from the sender's side, and if it looks like a reputation-based block on their sending IP or domain specifically, reporting a false positive block to Microsoft covers the paths available once you've confirmed it isn't anything in your own tenant.

Where WarmySender Fits in This Picture

To be direct about it: WarmySender has no access to, and no influence over, anyone's inbox rules, tenant mail flow rules, block lists, or message trace. That's entirely inside the recipient's own Microsoft tenant, controlled by them or their admin, and no outside tool - WarmySender included - can reach into it or check it on your behalf. If you're the sender working through this guide because your own outreach seems to be vanishing at one recipient's domain, this page's checklist is what your contact, or their IT team, would need to run, not something any sending platform can do for them.

What a sending platform can affect is how often you end up being the reason a message gets caught by any of the mechanisms above in the first place. WarmySender runs cold email campaigns, peer-to-peer email warmup, LinkedIn outreach, and multichannel sequences that combine channels in one flow, and the parts that matter here are the ones that keep your outbound looking unremarkable to begin with: gradual warmup on new or recovered mailboxes, paced sending instead of bursts, verified lists so bounces stay low, and mailbox health monitoring that flags a recipient domain gone quiet on your side before you've sent a dozen more messages into the same wall. When a specific contact does stop receiving your mail, that monitoring is what tells you it's worth asking them to run this checklist, instead of guessing. See how WarmySender works.