Cold email infrastructure starting at $1/mailbox. Volume discounts down to $0.55.Calculate your cost
ColdRelay
← All SMTP Errors
SMTP Error Reference

554 5.7.1

Microsoft 365: blocked by Exchange Online Protection content filter

Exchange Online Protection (EOP) classified the message as spam or malicious and rejected it. Permanent. Diagnose via headers, rewrite content, or work to improve sender reputation.

Last updated: May 23, 2026


Overview

What 554 5.7.1 Means

What it means

Exchange Online Protection (EOP) is Microsoft's anti-spam and anti-malware layer in front of every Microsoft 365 mailbox. 554 5.7.1 with descriptive text like 'blocked by content filter' or 'spam confidence level' is EOP rejecting because the message's content or sender reputation tripped a filter rule. 554 is a more definitive permanent reject than 550 — it indicates EOP refused the entire transaction.

Who you'll see it from

Exchange Online / Microsoft 365 inboxes protected by EOP (default for all M365 tenants). On-premises Exchange with Defender for Office 365 produces similar codes.

Why it happens

Message body contains content matching EOP's spam fingerprints; sender IP has high spam confidence level (SCL); sender domain is on Microsoft's reputation blocklist; attachment matched malware signature or unsafe-attachment policy; URL in message points to a Microsoft-flagged domain; or message structure matches known phishing patterns.

Resolution

How to Fix 554 5.7.1

  1. 1

    Look at the X-Microsoft-Antispam header from the bounce

    When EOP rejects, the bounce message often includes diagnostic headers. Look for X-Microsoft-Antispam, BCL (Bulk Confidence Level), SCL (Spam Confidence Level), or PCL (Phishing Confidence Level) headers. The numeric values tell you which filter fired.

  2. 2

    Audit your message for spam triggers

    Run the message HTML through coldrelay.com/tools/can-spam-checker. EOP weighs heavily on subject-line manipulation ('Re: re: re:'), all-caps text, excessive emoji, link-shorteners, image-only content, and HTML/text mismatch. Fix every flagged issue before resending.

  3. 3

    Check your sender authentication

    EOP's first-pass filter weighs authentication heavily. If SPF, DKIM, or DMARC fail or don't align, content filters become more aggressive. Run the Email Deliverability Test at coldrelay.com/tools/email-deliverability-test to confirm all three pass and align.

  4. 4

    Verify IP reputation in SNDS

    Microsoft's SNDS dashboard (sendersupport.olc.protection.outlook.com/snds) shows your IP's reputation tier. Yellow or Red tier means EOP's content filter is significantly more aggressive for your traffic. Recovery requires sustained low-volume clean sending over 2-4 weeks.

  5. 5

    Submit a sender-feedback ticket if needed

    If you've fixed authentication, content, and reputation but still see 554 5.7.1, submit a delisting request at sender.office.com. Include the bounce headers, your SPF/DKIM/DMARC status, recent sending history, and remediation summary. Microsoft typically responds within 24-72 hours.

    Note: Don't submit a delisting request without first resolving the underlying issue — Microsoft tracks repeat requesters and lowers review priority for them.

  6. 6

    Move to dedicated infrastructure if on shared IPs

    Shared-IP sending environments accumulate EOP penalties from every customer's bad behavior. If you're on shared infrastructure, the structural fix is dedicated IPs. ColdRelay provisions dedicated IPs per customer on isolated Azure tenants — your IP's EOP reputation is entirely your own.

Authority

References

Cold email infrastructure

554 5.7.1 in the Cold Email Context

EOP rejections are the dominant cold email problem for B2B outreach because Microsoft 365 dominates enterprise inbox share. EOP weighs authentication, IP reputation, content, and sender history into a single decision per message — fixing one component partially helps; fixing all simultaneously is what changes outcomes. ColdRelay addresses three of the four (auth via auto-DNS, IP reputation via dedicated IPs on isolated Azure tenants, sender history via clean provisioning); the fourth (content) is the operator's discipline. The Sends log surfaces Microsoft-specific bounces separately from other receivers so you can see which sends are failing at EOP vs. Gmail's filters.

FAQ

Frequently Asked Questions

What is EOP and how is it different from Defender for Office 365?

EOP (Exchange Online Protection) is the baseline anti-spam/anti-malware layer included with all Microsoft 365 mailboxes. Defender for Office 365 adds enhanced protections (safer attachments, Safe Links, anti-phishing AI) on top of EOP. From a sender's perspective, both reject with the same code categories; the difference is in detection aggressiveness on the recipient side.

What's a Bulk Confidence Level (BCL)?

BCL is EOP's bulk-mail rating, 0-9, where 0 means 'definitely not bulk' and 9 means 'definitely bulk'. Cold email almost always gets a non-zero BCL because it's literally bulk-pattern sending. Lower BCL (clean lists, low-spam-complaint history) reduces aggressive filtering.

How long does EOP reputation recovery take?

Typically 2-6 weeks of consistent good behavior. Recovery means: low complaint rate, low spamtrap hits, clean authentication, no Microsoft delisting requests in your recent history. Sending at lower volume during recovery accelerates the timeline.

Can I bypass EOP for specific tenants?

Yes — recipient organizations can configure 'allow lists' that whitelist your sending domain or IP. This requires the recipient's IT team to take action. Useful for big customer relationships but doesn't scale across cold outreach to many tenants.

Keep reading

Related SMTP Errors and Guides

Stop Seeing 554 5.7.1 For Cold Email

ColdRelay ships clean, dedicated infrastructure with SPF, DKIM, DMARC, and reverse DNS configured automatically — the same fixes that resolve most 554 5.7.1 bounces. Starting at $50/month.

Start for $50/month →