Microsoft 365 Has Prevented the Delivery of New Emails: Complete Guide

Short answer: The genuine notice appears inside your own mailbox, addressed to you as the recipient, and it is not a bounce - the sender never sees it and never receives it as a message. If what you are looking at instead is an actual email sitting in your inbox with a button asking you to sign in, verify, or resend on someone else's behalf, stop before clicking anything: that pattern matches documented phishing campaigns that impersonate exactly this kind of notice.

• If this is a genuine in-mailbox notice naming a contact: work the recipient checklist below in order - mailbox storage first, then rules, then connected accounts, then blocked senders.
• If what you're looking at is an email with a link asking you to sign in or "release" messages: read the phishing section before you click anything.
• If you are the sender and someone told you about this notice: you almost certainly did not receive a bounce, and the fix is not on your end - see the sender section near the bottom.
• If you were actually told about quarantined mail, not this specific notice: that is a different, real Microsoft feature with an actual release mechanism, covered separately in this guide.

The Exact Notice, Explained

People search this one almost word for word because the wording is specific enough to paste directly into a search engine: Microsoft 365 has prevented the delivery of some number of new emails from one of your contacts to your inbox, due to an unknown server error. It reads like something urgent went wrong, and it is aimed squarely at the person receiving mail, not the person sending it.

That last part is the single fact that resolves most of the confusion around this notice. It appears inside your own mailbox interface, describing something that happened on the receiving side of a delivery attempt. It is not addressed to the sender, the sender never sees this exact wording, and it is not the same thing as a bounce or non-delivery report, which is a completely different mechanism that goes back to whoever sent the message, not to you.

This guide goes deep on one notice: what it means, how to tell a genuine version of it apart from a phishing lookalike, exactly what to check in your own mailbox, and what "recovering the mail" actually looks like once you understand it is not a message sitting somewhere waiting for a button to be pressed. If what actually landed in your NDR or your admin console instead names a specific mail flow rule rather than this wording, that is a different, more clear-cut situation covered in a custom mail flow rule has blocked your message. The broader Microsoft delivery-failure landscape - bounce codes, junk placement - is covered across the rest of the guides library, including Outlook blocking your emails, which touches this same notice briefly as one entry in a wider table.

Is This Notice Real, or a Phishing Attempt

Ask this question before anything else, because the honest answer is that both versions exist, and one of them wants your password.

Security researchers have documented phishing campaigns that specifically imitate Microsoft 365 and Office 365 non-delivery notifications - fake messages claiming several emails could not be delivered, styled convincingly with familiar branding, that ask the recipient to click a button to review, verify, or resend the affected messages. The button leads to a credential login page that is not actually hosted on a Microsoft domain, and the entire goal is to capture the account password typed into what looks like a normal sign-in box.

A genuine notice about a delivery problem with your own mailbox has a specific, checkable shape, and a phishing attempt built to imitate it usually breaks that shape in at least one of these ways:

The single most reliable test: never type your email password into a page you reached by clicking a link in a message, regardless of how official it looks. If you want to check your account for a genuine issue, close the message and open a new browser tab, then navigate to outlook.com or office.com directly, the same way you would on any other day. If there is a real problem, it will be visible from your own mailbox without needing to follow any link at all. If a page asks you to "verify" your identity by entering your password before showing you anything, treat that as confirmation it is not genuine, not as a hurdle to get past.

One more honest point: Microsoft's own wording for this class of in-product notice is deliberately generic, and that same plain, non-urgent, non-actionable phrasing is exactly why it gets convincingly imitated. The fact that a message reads exactly like the phrase people search for is not, by itself, proof either way - the shape of what it asks you to do is what actually tells the two apart.

What "Unknown Server Error" Actually Covers

Treat this phrase as a label, not a diagnosis. Microsoft does not publish a breakdown of which specific technical fault sits behind it in any given case, and the wording is intentionally broad enough to cover several unrelated causes with one catch-all message, the same way a general-purpose app error might say "something went wrong" instead of naming the exact failure.

What it does tell you, reliably, is the direction of the failure: Microsoft's own systems attempted to complete delivery into your mailbox and could not finish that step. It is not describing a problem with the sender's outgoing mail server, even though the phrase "server error" makes that a natural first guess. The server involved is on Microsoft's side of the handoff, working with your mailbox, not the sender's side working to reach Microsoft.

Because the label does not narrow things down for you, the productive move is to stop trying to interpret "unknown server error" any further and instead work the checklist below, in order, since together those four causes account for the large majority of real cases behind this exact notice.

The Recipient Checklist, in Order

Each of the next four sections covers one cause in depth. Here is the summary to work from, fastest and most common first.

Work them in this order because each is progressively less common than the one before it, and there is no value in investigating an obscure sync failure before ruling out a full mailbox, which takes ten seconds to check.

Cause 1: Mailbox Storage

A mailbox sitting at or very close to its storage limit cannot accept new mail cleanly, and this is the most common cause behind this specific notice by a wide margin. The mechanism is intuitive once stated: incoming mail has to be written somewhere, and an account with no space left to write to fails in ways that read exactly like a generic, unexplained server-side problem from the outside.

To check it: open Settings, then General, then Storage, and look at how much of your allotment is used. If you are close to the limit, the fastest real wins are usually hiding in two places people forget to check - the Deleted Items folder, which does not always purge itself automatically the way people assume, and the Junk Email folder, which can quietly accumulate a large volume over time. Empty both, then look at your storage figure again before assuming you need to delete anything you actually want to keep.

If storage genuinely is full and you use the account for anything beyond casual mail, consider what is consuming the space beyond old messages - large attachments are usually the biggest single contributor, and searching by size rather than by date finds them far faster than scrolling.

Cause 2: Inbox Rules and Forwarding

Open your Rules list under Settings, then Mail, then Rules, and read every entry, not just the ones with obviously relevant names. This matters because the rule causing a problem is very often one you set up years ago for a completely different reason and have not thought about since.

What to look for specifically: any rule whose condition could plausibly match the sender named in the notice - by exact address, by domain, or by a keyword that might appear in their messages - paired with an action that moves, deletes, or forwards the message rather than simply flagging it. A Delete action is the most consequential, because it leaves nothing behind to find later. A Move action to an unexpected folder is nearly as disruptive and much easier to overlook, since the mail is technically still in your account, just not anywhere you would think to look.

Forwarding deserves its own mention. If your account forwards to another address, a failure at that second hop - the destination address closed, its own mailbox full, or the destination server rejecting the forwarded copy - can produce exactly this symptom even though your own mailbox accepted the message correctly in the first step. Forwarding also interacts with authentication in ways that can cause a second hop to reject mail that passed cleanly on the first, so a forwarding rule is worth checking even when it seems unrelated to a specific contact.

Cause 3: Connected and Synced Accounts

Outlook.com and the new Outlook app let you link other email accounts - Gmail, Yahoo, iCloud, another Outlook.com address - into one unified view, pulling their mail in alongside your primary account's own mail. This is convenient until the connection itself breaks, and when it does, the failure is often silent from your side: the linked account keeps receiving mail completely normally, it simply stops appearing inside the unified view you have been checking.

This produces a very specific, confusing symptom: the sender insists they sent the message, and they may even be right, because it may genuinely exist - sitting untouched in the other account, which you have stopped actively checking because you were relying on the sync to surface it for you.

To check: open Settings, then look for Sync email or Connected accounts, and review each linked account for an error state or a prompt to reconnect. Authentication for these connections expires periodically depending on the other provider, and a routine password change or security setting on that other account is a common, easily overlooked trigger.

Cause 4: The Sender Is on Your Blocked List

Open Settings, then Mail, then Junk email, and read your Blocked senders and domains list in full. An address lands here more easily than most people expect - a single accidental click on a Block option in a message's menu is enough, and there is no confirmation step that would have caught the mistake at the time.

This cause deserves a specific mention in the context of this notice, because a blocked sender does not typically produce a bounce back to them, so from their side everything looks normal - which lines up closely with the confusion this notice itself generates. For the complete walkthrough of managing this list, including its size limit and how to distinguish it from Junk filtering more broadly, see the dedicated section in Hotmail blocking your emails.

Why It Names "One of Your Contacts" Specifically

The wording is worth paying attention to in its own right. It does not say some incoming mail was filtered, or that your account had a generic problem - it names a delivery attempt tied to a specific relationship, someone already in your contacts or someone you have exchanged mail with before. Microsoft does not publish the exact detection logic behind when this particular notice fires rather than a more generic one, but the wording itself tells you what kind of event triggered it: something about repeated or specific delivery attempts from a known address, not a bulk filtering sweep across unrelated senders.

Practically, this is a useful piece of information rather than just phrasing. It means the notice is not describing your account's spam filtering broadly, and it is not describing a problem with mail in general - it is describing a specific relationship where something kept failing. That narrows your own investigation: focus the checklist above specifically on that one contact's address and domain rather than treating it as a sign that something is wrong with your mailbox as a whole.

This Notice Is Not the Same as Quarantine

It is worth being precise here, because people often search for how to "release" this notice's messages, and release is the correct word for a completely different Microsoft feature that this notice is not.

Quarantine is a real, separate mechanism inside Microsoft's filtering: certain messages, usually ones scored as likely spam, phishing, or malware, are held rather than delivered, and a genuinely quarantined message is sitting somewhere specific, retrievable through a specific interface, exactly the way the word "release" implies. The prevented-delivery notice this guide is about describes something different - a failed delivery attempt, not a held message. Nothing was quarantined. There is no holding area containing the messages the notice refers to, which is precisely why there is no release button anywhere in your account for this specific notice, no matter how long you search the interface for one.

The next two sections cover both halves of that distinction: how release genuinely works when mail actually is quarantined, since that scenario is common enough that people frequently conflate the two, and then what recovering mail actually means for this specific notice, which is a different process entirely.

How Release Actually Works for Genuine Quarantine

If what you are actually dealing with is quarantine - a separate notification, typically a periodic digest email listing specific held messages - the mechanics are well defined and genuinely include a release action.

• The quarantine notification itself lists affected messages with options attached to each one: release it to your inbox, report it as not junk, block the sender outright, or preview the message content before deciding.
• Whether you can release a message yourself depends on why it was quarantined. Ordinary bulk or spam-scored mail is commonly configured to allow the recipient to release it directly. Messages held for high-confidence phishing or malware are typically not releasable by an end user at all, regardless of how the notification is worded - an administrator has to make that call.
• You can also check quarantine directly rather than waiting for a digest, through the Microsoft 365 security portal if your account is a work or school account with access, where held messages are listed with the same release, report, and block options.
• If you are on a personal, consumer-only account, quarantine in this administered sense generally does not apply to you in the same way - consumer Outlook.com filtering routes unwanted mail to Junk directly rather than through an organization-level quarantine queue with its own release workflow.

If this is genuinely your situation, work from the notification or the quarantine list itself rather than anything in this guide's checklist - the two problems look similar in a search result but resolve completely differently.

Recovering the Messages This Notice Warned About

Here is the honest version of what recovery looks like for this specific notice, once you understand it is describing a failed attempt rather than a held message. There is nothing to release, because nothing was retained anywhere waiting for you.

1. Work the recipient checklist above and actually fix whatever it finds. Free up storage, correct or remove the rule, reconnect the failing account, or remove the blocked-sender entry - whichever applies.
2. Tell the sender plainly what you found and fixed. Specific beats vague: "my mailbox was full and I've cleared it" gives them a reason to try again with confidence, where "I don't know what happened" does not.
3. Ask them to send again, not to wait for anything to arrive on its own. Depending on how their own system handled the original failure, it may already have given up retrying entirely, so a fresh message is the reliable path rather than an assumption that a delayed copy is still coming.
4. If the same notice recurs for the same contact after you have fixed the obvious cause, revisit the checklist in order rather than assuming a new, more exotic cause - it is common for more than one small thing to be true at once, such as a mailbox that was both nearly full and had an old forwarding rule quietly active.

If You're the Sender Who Got Reported This

If a contact told you they saw this notice about mail from you, the most important thing to know is what it does not mean: it is not evidence that your sending is broken, and if you did not receive a bounce for the message in question, your side of the delivery attempt went as expected. Your server handed the message to Microsoft, Microsoft accepted it, and the failure happened after that point, entirely inside the recipient's own mailbox.

There is genuinely very little for you to do here beyond what the recipient checklist above already covers on their end. It is still reasonable to sanity-check your own authentication is passing cleanly - a quick look at the Authentication-Results header on a message delivered to an address you control - purely to rule out an unrelated, coincidental problem on your side, using the process in Outlook blocking your emails. But treat that as due diligence, not as the fix, because the fix for this specific notice lives entirely inside the recipient's own account settings.

Preventing This With WarmySender

Be direct about the limit here: this notice is generated inside your recipient's own mailbox, describing their own account's state, and WarmySender - or any sending tool - has no visibility into or control over another person's storage, rules, connected accounts or blocked-senders list. Nothing on the sending side fixes this notice, because nothing on the sending side caused it.

What WarmySender does is keep the sending half of any relationship with a Microsoft recipient as clean and predictable as possible, which matters for the broader Microsoft delivery picture even when it cannot touch this specific notice: cold email campaigns with per-mailbox daily sending caps and paced delivery, peer-to-peer email warmup that builds a real history for new mailboxes before they send in volume, inbox rotation, mailbox health monitoring, and list verification before you send. LinkedIn outreach and multichannel sequences run alongside the same accounts.

If a contact reports this notice, the productive response is the recipient checklist earlier in this guide, sent to them directly - not a change to your own sending setup. See how WarmySender works.