Published · Last verified · Maintained by TamingDNS

🪟 Microsoft 365 / Outlook SMTP Error Code Directory

Microsoft 365 bounce emails are packed with internal component names like RESOLVER and STOREDRV alongside standard SMTP codes, which makes them look far more intimidating than they are. This directory translates every Exchange Online rejection into plain English, with a fix for each one.

Provider
Microsoft 365 / Exchange Online / Outlook.com
Key Identifiers
RESOLVER · STOREDRV · protection.outlook.com
MX Hostname Pattern
*.mail.protection.outlook.com

How to Identify a Microsoft 365 Bounce

Microsoft 365 NDRs arrive from [email protected] or postmaster@<tenant>.onmicrosoft.com. The Diagnostic-Code often includes a proprietary component name like RESOLVER (routing/addressing) or STOREDRV (mailbox store delivery).

Diagnostic-Code: smtp; 550 5.7.13
  STOREDRV.Deliver.Exception:AccountDisabledException.MapiExceptionADUserDisabledAndHidden;
  Failed to process message due to a permanent exception with message [BeginDiagnosticData]...

The component prefix (STOREDRV, RESOLVER, QUEUE) tells you which part of Exchange Online rejected the message. See the glossary below.

Microsoft 365 Error Codes

17 codes with Microsoft 365-specific behaviour. Critical (Tier 1) codes appear first.

🟡 421 4.4.7 CRITICAL
Message Expired in Queue
Microsoft 365 uses 4.4.7 when your message cannot be delivered within 24 hours. NDR typically arrives with subject "Delivery delayed".
Full explanation & fix →
🔴 501 5.1.8 CRITICAL
Bad Sender Address
Microsoft 365 returns this when the sender domain cannot be found in DNS. Ensure your domain has valid DNS records.
Full explanation & fix →
🔴 535 5.7.8 CRITICAL
Authentication Credentials Invalid
Microsoft 365 may require Modern Authentication (OAuth 2.0) for SMTP. If Basic Auth is disabled, configure your client for OAuth.
Full explanation & fix →
🔴 550 5.1.1 CRITICAL
Mailbox Does Not Exist
Microsoft 365 returns: "Recipient not found by SMTP address lookup." Check the address in the GAL if sending to an internal mailbox.
Full explanation & fix →
🔴 550 5.2.1 CRITICAL
Mailbox Disabled
Microsoft 365 uses 5.2.1 when an Exchange Online mailbox has been disabled or the account has been deactivated.
Full explanation & fix →
🔴 550 5.4.1 CRITICAL
Recipient Address Rejected
Microsoft attributes 550 5.4.1 "Recipient address rejected: Access denied" to directory-based edge blocking rejecting an invalid recipient, and its published fixes are all recipient-side. One deliverability vendor's guide blames IP reputation, but Microsoft documents no reputation path for it. Microsoft lists a second 5.4.1, Relay Access Denied, for a server that does not accept mail for the recipient's domain. Test a second valid recipient before assuming either.
Full explanation & fix →
🔴 550 5.7.1 CRITICAL
Message Rejected by Policy
Microsoft 365 returns 5.7.1 when the sender IP or domain reputation is poor. Check with Microsoft SNDS.
Full explanation & fix →
🔴 550 5.7.13 CRITICAL
User Account Disabled
Microsoft's page for 550 5.7.13 and 550 5.7.135 covers a public folder that rejects external senders, and only an email admin in the recipient's organisation can fix it. Bounces naming STOREDRV and an AccountDisabledException also carry 5.7.13. Microsoft does not document that form.
Full explanation & fix →
🔴 550 5.7.14 CRITICAL
Trust Relationship Required
Microsoft 365 returns 5.7.14 when Basic Auth is disabled and the client hasn't migrated to Modern Auth. This is increasingly common as Microsoft rolls out Basic Auth deprecation.
Full explanation & fix →
🔴 550 5.7.23 CRITICAL
SPF Validation Failed
In Exchange Online you get 550 5.7.23 as the sender: the destination system checked SPF and rejected your outbound message. Microsoft points the fix at your own tenant. Check your SPF record, provision every domain you send from, and add any on-premises IPs. Also check whether the message went out through the High Risk Delivery Pool, whose mail fails SPF.
Full explanation & fix →
🔴 550 5.7.26 CRITICAL
Multiple Authentication Checks Failed
Microsoft does not issue 5.7.26. The code does not appear in Exchange Online's NDR code table, and Microsoft's own outbound-deliverability post quotes the 550-5.7.26 string as one Gmail returns to mail sent from Microsoft 365. Microsoft's own authentication rejection is 550 5.7.515: from May 2025, Outlook.com, Hotmail and Live require SPF and DKIM to pass plus a passing DMARC check from any domain sending 5,000 or more messages a day.
Full explanation & fix →
🔴 550 5.7.515 CRITICAL
Outlook Rejects Unauthenticated High-Volume Sender
Microsoft's NDR page for 550 5.7.515 covers Outlook.com, Hotmail, Live.com and MSN. It applies once you send 5,000 or more messages using the same From domain. Both SPF and DKIM must pass, a DMARC record must be published, and the message must pass DMARC. Mail that falls short is rejected.
Full explanation & fix →
🔴 552 5.2.3 CRITICAL
Message Too Large for Mailbox
Microsoft 365 has a 25 MB default receive limit. This can be raised by Exchange admins up to 150 MB.
Full explanation & fix →
🔴 552 5.3.4 CRITICAL
Message Too Big for System
Microsoft 365 default system limit is 25 MB. Enterprise plans can configure up to 150 MB per organisation.
Full explanation & fix →
🟡 451 4.7.1
Temporary Auth / Policy Hold
Microsoft 365 uses 451 4.7.1 for DMARC-related temporary deferrals. Fixing alignment usually resolves it.
Full explanation & fix →
🔴 550 5.2.4
Mailing List Expansion Problem
Microsoft 365 returns 5.2.4 when a distribution group cannot be expanded, often due to a disabled owner or a group with no members.
Full explanation & fix →
🔴 550 5.7.25
Reverse DNS (PTR) Validation Failed
Microsoft documents 5.7.25 for IPv6 only: "Access denied, the sending IPv6 address [...] must have a reverse DNS record". Anonymous inbound mail over IPv6 is opt-in for a Microsoft 365 organisation. Once it is on, a source IPv6 address without a valid PTR record gets the deferral 450 4.7.25.
Full explanation & fix →

Microsoft NDR Component Glossary

The component prefix in an Exchange Online NDR tells you which subsystem rejected or failed to deliver the message.

RESOLVER
Routing and address resolution layer. Errors here mean Exchange couldn't find or route to the recipient's mailbox.
STOREDRV
Store Driver: the component that writes messages to the mailbox database. Errors here mean the mailbox exists but can't accept messages (disabled, locked, full).
QUEUE
Mail queue: appears in 4.4.7 (expired) and other delivery-delay NDRs. Indicates the message spent too long waiting to be delivered.
FilteringService
Exchange Online Protection (EOP) anti-spam and policy engine. Errors here mean your message was blocked by Microsoft's inbound filtering rules.

Microsoft Sender Tools

Microsoft provides two free tools for senders who are being blocked by Exchange Online:

Delist Portal
If your NDR reads 550 5.7.606 to 5.7.649, "banned sending IP", request removal here. A 5.7.511 cannot use the portal: forward the NDR to [email protected] instead.
sender.office.com →
SNDS (Smart Network Data Services)
Shows the complaint rate and block status for IPs sending to Microsoft 365 mailboxes. Free to register.
SNDS portal →

Frequently Asked Questions

Common questions about Microsoft 365 SMTP errors and Exchange Online NDRs.

NDR stands for Non-Delivery Report, Microsoft's name for the bounce email you receive when Exchange Online cannot deliver your message. NDRs always include a status code like 5.7.23, and often include a component name like STOREDRV or RESOLVER that tells you which part of Exchange rejected the message. That component name is the fastest way to narrow down the cause.

Microsoft lists two meanings for 5.4.1, and the text beside the code tells them apart. Its NDR list gives "Relay Access Denied" to a server that does not accept mail for the recipient's domain. "Recipient address rejected: Access denied" is directory-based edge blocking rejecting an invalid recipient, and every fix Microsoft lists is recipient-side. Senders also report that one with SPF, DKIM and DMARC all passing. Microsoft publishes nothing confirming a reputation path for this code. Send to a second address you know is valid at the same organisation. If only one bounces, the address is the problem. If every recipient there bounces, Microsoft's fix is still on their side: its troubleshooting page has their admin resync the accepted domain. Only if that changes nothing, and SPF, DKIM and DMARC all pass, check your sending IP with our Blacklist Checker and the Microsoft delist portal.

Microsoft is phasing out the old username-and-password method of SMTP authentication (called Basic Auth) in favour of OAuth 2.0, which is what they call Modern Authentication. If you get a 5.7.14 error, it means the email client or app you are using is still trying to log in the old way on an account where Microsoft has turned that off. The fix is to update your client or application to use OAuth 2.0. Older SMTP libraries often need a code change to support this.

Read the text beside the code. Microsoft documents 5.7.13 for a public folder that rejects mail from outside the organisation, and only an email admin in the recipient's organisation can change that. The IANA registry names the code "User Account Disabled": an account disabled after a successful sign-in, which points at your own sending account. Senders also report bounces naming STOREDRV and an AccountDisabledException with this code. Microsoft does not document that form, so ask the recipient's IT team rather than guess.

🔍

Got a Microsoft 365 bounce to decode?

Paste your full NDR email or SMTP error line for an instant plain-English diagnosis.

Open the Bounce Decoder →