What causes the 552 5.2.2 size exceedance error in Microsoft 365?

You send a message, everything looks fine, and then—bounce. The error log says 552 5.2.2: size exceedance. You check the attachment: it’s under 100 MB. So why did it fail?

The answer is not what you think. It’s not about file size alone. Microsoft 365 enforces a strict 150 MB limit on entire messages—not just attachments. Headers, body text, inline images, and embedded content all count.

Even if your file is small, a single large image embedded in HTML, a dozen inline thumbnails, or rich formatting in your template can push the total volume over the limit. This applies to every email, regardless of sender reputation or destination domain.

Key takeaways

  • Microsoft 365 enforces a 150 MB limit on the full message, including headers, body, and all embedded content.
  • Size exceedance occurs even if the attachment alone is under 150 MB due to cumulative payload from inline images, HTML, or embedded objects.
  • Neither sender reputation nor domain type affects the 150 MB constraint—this rule applies to all inbound and outbound email traffic across the platform.

How does email size exceedance impact deliverability and sender reputation?

Repeated 552 5.2.2 size exceedance errors can lead to Microsoft 365 throttling your sending rate or triggering temporary rejections, even if individual messages aren’t blocked. While these errors don’t directly harm sender reputation, they signal poor message hygiene to filtering systems. Over time, frequent size issues may be logged as anomalies, increasing the likelihood of delayed delivery or inbox filtering—even for valid messages.

Size limits are enforced, not ignored

Microsoft 365 enforces a maximum message size of 150 MB per email, including headers, body, and all attachments. When you exceed this, the server returns a 552 5.2.2 error. This isn’t a soft bounce—it’s a hard rejection at the transport layer. If this happens repeatedly from the same sender, Microsoft’s systems begin to treat your send volume as abnormal, even if delivery rates otherwise appear stable.

Let’s say you send a weekly newsletter with a 160 MB PDF attachment to thousands of recipients. Each message fails with 552 5.2.2. The system logs these failures consistently. Even if your authentication (SPF, DKIM, DMARC) is clean and your IP isn’t on a blocklist, the pattern raises red flags. Microsoft uses patterns like this to detect potential abuse, which can result in rate limiting or delayed delivery for all messages, not just oversized ones.

Even indirect effects matter

Sender reputation is built on consistency, reliability, and compliance. A single 552 5.2.2 error may not hurt your score, but a recurring one does. It suggests you’re not validating your list, not checking attachment sizes, or not optimizing content. Filtering systems like Microsoft’s built-in anti-spam engine analyze these patterns to assess legitimacy.

Research from Return Path shows that senders with consistent delivery anomalies—like repeated size errors—are more likely to have their emails routed to junk folders, even when they follow best practices otherwise. Inconsistent delivery behavior degrades the perceived trustworthiness of your domain.

To avoid this, validate your email list regularly. Remove invalid or outdated addresses before sending. Use tools that check for oversized attachments during content prep. For teams managing large-scale campaigns, consider splitting content into multiple emails or using external file-sharing links.

Tools like bulk email list cleaning can help you catch oversized attachment risks early—by identifying inactive, invalid, or misformatted addresses that often come with malformed or heavy content. You can also test inbox placement with real user inboxes using inbox placement reporting, which helps expose delivery gaps before they become widespread.

What is the difference between a 552 5.2.2 error and a rejected bounce?

A 552 5.2.2 error means your message was too large for Microsoft 365 to accept, not that the recipient address is invalid or inactive. Unlike a rejected bounce (which may stem from a non-existent address or policy block), this error reflects a configuration issue on the receiving end — specifically, a size limit being exceeded. It doesn’t impact list health, only delivery success.

How a 552 5.2.2 error appears in Microsoft 365 logs

You’ll see it in mail logs as a permanent failure (5xx code) with the exact status: 552 5.2.2. This is a clear signal from the receiving server: “I can’t accept this message — it’s over the allowed size.” Microsoft enforces a 100 MB limit on incoming messages by default in Microsoft 365, including all attachments and headers. If your email exceeds that, the server rejects it outright.

It’s important to distinguish this from soft bounces like 4xx codes, which often indicate temporary issues like a full inbox or server downtime. A 552 5.2.2 is not temporary — it’s a firm refusal due to size. It’s also not a hard bounce like 5.1.1 (unknown user), which would point to an invalid or non-existent email address.

Why this error doesn’t mean your list is bad

Just because a message fails to deliver due to size doesn’t mean the email address is wrong. The user is active — they’re just getting blocked by a policy. This is why you should treat 552 5.2.2 as a configuration issue, not a list quality issue.

For example, if you’re sending a 150 MB email with multiple attachments, even a valid address in Microsoft 365 will get 552 5.2.2. You aren’t hitting a bad address — you’re hitting a rule. The same address might accept the same message on Gmail, which uses a 25 MB limit for mail (though larger with cloud attachments).

Properly sized content reduces rejection risk. Tools like bulk email list cleaning can help spot problematic senders or oversized campaign drafts before they go out, but the core fix is in content size, not contact validation.

For deeper context, the standards around SMTP error codes are defined in RFC 5321, which specifies the structure of 5xx responses like 552 5.2.2. This section of RFC 5321 details how receivers should respond to unacceptable message size.

How to identify and resolve 552 5.2.2 errors in your sending workflow

When Microsoft 365 rejects your email with a 552 5.2.2 error, it means the message exceeds the recipient’s size limit—typically 100 MB for inbound messages. Check the total size of your email, including attachments, embedded content, and rendered HTML, before sending. Use tools that simulate real delivery conditions to catch size issues early. Avoid embedding large assets directly; host them externally instead. This reduces payload without sacrificing user experience.

Inspect the full message size before sending

  • Use a tool that measures the complete email payload, including headers, body, and attachments, as it would be sent over SMTP—RFC 5321 defines the standard message format.
  • Test with a real-world sending environment, not just a local preview. Rendering engines can differ across clients.
  • Verify the final output size, especially after templating engines expand content.

Optimize content and avoid oversized payloads

  • Never embed files in your email body. Instead, link to them via cloud storage (e.g., OneDrive, Google Drive) and include a download button.
  • Check image and media sizes in your HTML templates—compressed files still consume space when rendered. Serve responsive assets.
  • Remove unnecessary inline CSS, especially if duplicated across multiple elements. Large style blocks inflate message size without benefit.
  • Do not include JavaScript in your emails—Microsoft 365 blocks it, and it increases size and risk.
  • Use a service like bulk email list cleaning to validate entire lists and exclude addresses that are dead or likely to bounce due to size filters.
Size limits aren’t arbitrary—they’re designed to prevent abuse and manage server load. A single oversized message can affect deliverability for many users.

Let’s be clear: you can’t rely on clients to handle large emails gracefully. If your content exceeds 100 MB, Microsoft 365 will return a 552 5.2.2 error no matter how well you’ve crafted the message. The fix starts before sending: simulate the full journey using end-to-end verification tools that include payload inspection. Even if your template looks fine in a browser, real email clients may render it differently—especially with embedded media.

Treating every email as a potential delivery failure is a best practice. Tools that analyze sender reputation, attachment size, and content rendering give you full visibility before you hit the inbox. For teams that send at scale, combining real-time verification with pre-send size checks reduces hard bounces and maintain consistent deliverability.

When list hygiene helps prevent 552 5.2.2 errors

552 5.2.2 errors in Microsoft 365 often stem from sending oversized content to too many recipients at once—something clean email lists directly reduce. If your list includes outdated, duplicate, or irrelevant addresses, you risk sending the same bulky message to hundreds of unverified inboxes, triggering size limits even if the content itself is fine.

Bad list hygiene inflates send volume unintentionally

Let’s say you’re sending a 15MB PDF newsletter. If your list has 10,000 entries, but 3,000 are invalid or duplicates, you're still sending 15MB to 7,000 people—some of whom are inactive, misaddressed, or on outdated domains. That volume alone can flag your outbound mail as suspicious, especially if the same content hits high-touch domains like Outlook or Gmail.

Microsoft’s infrastructure applies threshold-based filtering: consistent large-volume sends—even to valid recipients—can trigger 5.2.2 errors if they exceed per-hour or per-domain rate limits or appear behaviorally risky. A clean list reduces your overall send volume, making your delivery patterns less likely to hit those thresholds.

Size issues aren’t always about the content—sometimes they’re about volume

The actual size of your email doesn’t always cause 552 5.2.2 errors. It’s often the aggregate volume sent to Microsoft 365 domains that triggers the block. If your list has 10,000 users but 3,500 are invalid or low-quality, you’re sending too much data to too many places too quickly—this behavior mimics spam.

Regular list hygiene removes dead, duplicate, and non-engaged addresses. That means fewer total messages, lower aggregate size, and more predictable delivery. It’s not just about fixing bounce rates—it’s about avoiding the hidden triggers Microsoft uses to protect its network.

Tools like bulk email list cleaning can identify invalid addresses, catch-all domains, and role-based emails before you send, reducing accidental volume spikes. You don’t need to eliminate every oversized email—just avoid sending large content at scale to unverified or low-quality inboxes.

To avoid overloading recipient systems, Microsoft and other providers use rate-limiting and content-size checks at scale. Maintaining a lean, well-verified list is one of the most effective ways to comply with those limits. You can read more about outbound email policies from Microsoft Learn, which outlines how size and volume thresholds operate in practice.

When your email list includes invalid, dormant, or oversized recipient addresses, sending at scale increases the risk of hitting Microsoft 365’s 5.2.2 size exceedance threshold. Email List Validation’s bulk verification identifies and removes these addresses before they’re sent, reducing overall message volume and eliminating risky inboxes that could cause delivery failures due to size limits. This step keeps your send volume within acceptable bounds for individual recipients and the Microsoft 365 infrastructure.

How list hygiene stops oversized sends

Large email campaigns often push past size limits when they include outdated or improperly formatted addresses, especially if they’re routed through services like Mailchimp or SendGrid that aren't validating recipients in real time. Without verification, you might unknowingly send a message to 10,000 people, many of whom are invalid or auto-rejecting — each failure inflates the total envelope size and may trigger a 552 5.2.2 error. By cleaning your list beforehand, you reduce the number of recipients, which directly lowers the total message payload.

Let’s say your list has 5% invalid addresses. That’s 500 addresses per 10,000. If any of those are catch-all inboxes—or worse, auto-responding ones that reply with large bounce messages—you risk hitting size thresholds even with a small message. Email List Validation’s real-time verification flags these before sending, so you’re not accidentally sending to addresses that trigger large feedback loops. Bulk email list cleaning ensures only known, deliverable addresses receive your message, keeping individual deliveries within size constraints.

Validation during curation keeps messages lean

When you validate during list curation—before even thinking about sending—you’re not just improving deliverability. You’re also preventing the creation of oversized messages in the first place. For example, if your campaign uses large embedded images and attachments, each extra recipient increases the likelihood of a size exceedance. With a cleaned list, you send fewer messages, reducing the chance of hitting the 25MB or 10MB limit enforced by Microsoft 365 depending on the user’s configuration and transport path.

Spamhaus and other email security providers note that oversized messages are a common vector for abuse, so mail servers like those in Microsoft 365 are configured to aggressively reject those that exceed size limits. Spamhaus observes that many delivery failures attributed to spam filters are actually size-related. Proper list hygiene, enforced by tools like Email List Validation, prevents the problem before it starts. This isn’t about volume alone — it’s about sending only to addresses that reliably accept your message without triggering protocol-level rejections.

How to verify list health before sending to avoid size limits

Before sending bulk emails in Microsoft 365, validate your list in real time using a trusted verification service. This catches invalid, catch-all, or role-based addresses that inflate list size and trigger 552 5.2.2 errors. Combine this with a hard size check—block sends if the total payload exceeds 120 MB—and avoid attachment bloat before the message even leaves your server.

Use real-time verification in your production workflows

  • Integrate the Email List Validation API directly into your sending pipeline to validate addresses as they’re added or before mass sends.
  • Filter out addresses flagged as "catch-all" or "role-based" — these often route to shared inboxes or auto-replies and aren't reliable delivery endpoints.
  • Let the API return a clear verdict: valid, invalid, risky, or catch-all. This data is accurate to 98.9% and reduces false positives common in simpler tools.

Enforce size controls proactively

  • Before sending, calculate the total size of your message: include all attachments, body text, headers, and embedded content.
  • If the total payload exceeds 120 MB, split large attachments into smaller files or compress them using standard formats like ZIP or PDF.
  • Microsoft 365 enforces a 150 MB cap per message, but delivery fails if the final size exceeds 120 MB after processing — this is an industry-standard limit used by most enterprise email systems.
  • Use automation to flag or block sends that trigger size warnings, especially in campaigns targeting large lists.
The 552 5.2.2 error in Microsoft 365 is not a failure of your content—it’s a signal that the message exceeds size thresholds or has routing issues. Addressing it at the list level is more effective than troubleshooting individual bounces.

For a deeper check, test your message in real inboxes via inbox placement testing. This confirms how your message lands in actual user folders, not just on the server.

What does a 552 5.2.2 error look like in Microsoft 365 mail logs?

A 552 5.2.2 error in Microsoft 365 mail logs appears as "552 5.2.2 Message size exceeds maximum allowed" and typically follows a recipient address, the sending domain, and a timestamp. It indicates the message was rejected due to size, not sender reputation or domain issues. Logs often include the exact byte size of the message, which lets you isolate oversized attachments or content.

How the error appears in logs

You’ll see it in the "MessageDetails" section of the mail log, usually with a line like: 552 5.2.2 Message size exceeds maximum allowed (10485760 bytes). The number after "allowed" is the threshold—10MB in most standard Microsoft 365 tenants, per Microsoft’s documentation. This threshold can vary by tenant policy, but 10MB is common.

The error doesn’t signal a problem with your domain, SPF, or DKIM alignment. It means the message body—especially attachments, embedded images, or large HTML—surpassed the limit. This is especially common in bulk emails with rich content or in automated workflows that include file attachments without size checks.

Why size errors happen—and how to fix them

Common causes include PDFs, ZIP files, screenshots, or embedded videos in HTML emails that weren’t optimized. It also happens if you include base64-encoded images in email bodies or use untrimmed media in newsletters. Even a single large attachment can push a message over the line.

Let’s say your marketing email includes a 12MB PDF attachment. Even if the sender's domain is clean, the recipient's mail server (like Outlook or Teams) will reject it. The logs don’t tell you who’s at fault—only that the message failed due to size.

You can use tools like bulk verification to audit and clean your list before sending, ensuring you only target addresses that are likely to receive your content—reducing the risk of delivery failure due to size or reputation issues. But first, check your message size: if your email consistently exceeds 9MB, reduce the payload or serve attachments via a secure link.

How to test inbox placement with size limits in mind

You can simulate how your emails behave in Microsoft 365 environments by testing inbox placement with realistic content, including attachments, using Email List Validation’s inbox-placement tool. This helps catch 552 5.2.2 size exceedance errors before they hit real inboxes, especially when sending to Outlook or Teams users who enforce strict size limits.

Test with real-world content

  • Use Email List Validation’s inbox-placement testing to send messages with full body content, real attachments (PDFs, images, ZIPs), and embedded links as they’ll appear in production.
  • Test at or near the 25 MB size limit common in Microsoft 365 — a threshold your email will hit or exceed if you include large files or rich media.
  • Check results across different domains (e.g., @outlook.com, @gmail.com, @company.com) to see how each inbox handles large messages, not just Microsoft 365 accounts.
  • Review rejection logs with the 552 5.2.2 error specifically — it’s a clear signal your message exceeded the recipient’s size threshold, even if your sending server says otherwise.

Validate consistency across inboxes

  • Compare delivery outcomes across major providers: Outlook, Gmail, Yahoo, and others to see how your size-heavy emails fare in different environments.
  • Use real test domains, not just internal ones — some filtering behaviors differ based on domain reputation, which can affect size thresholds.
  • Run tests with and without attachments to isolate whether size is the actual cause of delivery failure.
  • Check how the email renders post-delivery: some messages pass size checks but get quarantined due to content policies — size isn’t the only factor, but it’s the one you can control early.

Microsoft's own documentation confirms that transport agents will reject messages that exceed size limits, often citing 552 5.2.2. The exact threshold may vary, but 25 MB is a commonly enforced hard limit in Exchange Online. You can verify this through Microsoft’s official documentation on message size limits.

Let’s be clear: size limits aren’t just about file size. They include embedded content, headers, and even encrypted content that expands the payload. You can’t rely on just testing with text messages. You need full-stack simulations.

Want to test inbox placement with real content and real size limits? Try our inbox-placement tool, specifically designed for this—test full messages with attachments and see how they land across popular inboxes, including Microsoft 365. Test inbox placement with real-world conditions here.

How Email List Validation supports clean, size-compliant lists

Verifying your email list before sending reduces bounces and size-related errors like 552 5.2.2 by catching invalid, catch-all, and risky addresses early. With 98.9% accuracy, Email List Validation identifies these issues at scale, preventing oversized or rejected messages. This means fewer wasted sends and better inbox placement in Microsoft 365 and other platforms.

Prevent size exceedances by cleaning your list before send

When you send to hundreds or thousands of addresses, even a few invalid or catch-all emails can lead to errors like 552 5.2.2. These happen not just from message size, but from delivery attempts to non-existent or oversubscribed inboxes. Email List Validation catches these during bulk verification, helping you send only to addresses that will accept your message.

Let’s say your list includes 10,000 contacts. Without validation, 10% might be inactive or misaddressed. That’s 1,000 addresses that could trigger a size exceedance during delivery, especially if the server treats them as valid until the connection fails. A clean list reduces the number of failed connections and keeps your overall send volume in checking with Microsoft 365's size limits.

Integrations and AI help you act fast and stay compliant

You can run validations directly before sending via integrations with SendGrid, HubSpot, Klaviyo, and Mailchimp. These sync with your existing workflows, so you catch issues before messages go out. That’s critical: Microsoft 365 enforces strict size and validity rules, and sending to invalid addresses can impact your sender reputation over time.

If your logs show recurring 552 5.2.2 errors, the in-app AI assistant can help you interpret them. It might suggest trimming your list, improving segmentation, or validating before every campaign. This level of insight is hard to get otherwise — especially when dealing with complex delivery failures across multiple platforms.

Start with 100 free verifications — no risk, no expiry. Purchased credits never expire, so you can scale as needed. For more details on how bulk validation works, see how to clean your list in bulk. To check inbox placement or automate verification, explore the integration options or the real-time API. For context on deliverability limits, see Microsoft’s official documentation on message size policies via the Microsoft documentation.

Preventing 552 5.2.2 errors: the ultimate checklist

552 5.2.2 size exceedance errors in Microsoft 365 are not just technical hiccups — they’re signals of inbox placement risk, wasted sends, and damaged sender reputation. Preventing them begins with treating every email as a deliverability test.

Core strategies to avoid size exceedance

  • Verify every address in your list before sending — invalid or catch-all addresses can inflate effective message size and trigger unnecessary rejections.
  • Host attachments externally. Embedding large files directly in emails often pushes messages beyond the 25 MB limit enforced by Microsoft 365.
  • Use inbox-placement tools to test your actual message size and content profile before sending to large segments.
  • Break down large messages into smaller, focused campaigns. This improves engagement and reduces fail rates.
  • Avoid bloated HTML templates with oversized embedded images, duplicate styles, or unnecessary code.
  • Monitor send logs regularly. When 552 5.2.2 errors appear, trace them to sender domains and analyze content size to identify root causes.

The most effective defense against size-related rejections is a proactive, data-driven process. Accuracy in list hygiene, disciplined content design, and real-time feedback loops are the foundation of consistent deliverability.

Sources

  • Segmented campaigns also protect list health, driving 9.37% fewer unsubscribes, 4.65% fewer bounces, and 3.90% fewer abuse reports than unsegmented sends. — Mailchimp (2025)
  • 65.62% of newsletter creators send weekly, compared with 15.82% sending daily and only 6.27% sending monthly. — beehiiv (2025)

Keep reading

Ready to put this into practice? Email List Validation verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What is the message size limit in Microsoft 365?

Microsoft 365 enforces a 150 MB limit on the total size of each message, including headers, content, and attachments.

Can a 552 5.2.2 error be a sign of spam?

No, 552 5.2.2 is a size-based delivery error, not a spam indicator. It occurs when the message exceeds Microsoft’s size limit regardless of content.

How do I test for 552 5.2.2 in my campaigns?

Use inbox-placement testing tools like Email List Validation to simulate delivery under Microsoft 365 conditions before sending.

Does a 552 5.2.2 error affect sender reputation?

It does not directly impact sender reputation, but consistent failures may trigger system-level warnings or delays.

Should I compress attachments before sending?

Yes. Compressing attachments reduces message size and helps avoid 552 5.2.2 errors, especially when sending to large lists.

Do role-based or catch-all addresses cause 552 5.2.2 errors?

No. These addresses are unrelated to message size. However, sending to invalid or catch-all addresses increases the risk of failure due to non-delivery.

Can email verification tools prevent 552 5.2.2 errors?

Yes — by cleaning lists and reducing unnecessary sends, verification tools help avoid sending oversized content at scale.

How accurate is Email List Validation?

Email List Validation has a 98.9% accuracy rate in identifying valid, invalid, and risky email addresses across large databases.

Do Email List Validation credits expire?

No, purchased verification credits never expire. You can use them at any time, even months later.

Can I test with 100 free verifications?

Yes. You can start with 100 free verifications to test list quality and delivery readiness without commitment.