Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 552 5.3.4 Message size exceeds fixed maximum message size | NDR email to sender | -> |
| Affected build range | Microsoft 365 / Exchange Online | Product documentation | |
| Registry key or OMA-URI involved | |||
| Relevant service/endpoint URL | https://admin.exchange.microsoft.com | Exchange admin center | -> |
| Log line signature | status 'Failed', reason 'MessageTooLarge' | Get-MessageTrackingLog |
Log Files to Check
C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceLogs\HealthService.log/var/log/exchange/MessageTracking
What This Error Actually Means
The error code "552 5.3.4 Message size exceeds fixed maximum message size" is raised by Exchange Online's transport service when an email message or its attachments exceed the configured maximum allowed size for inbound or outbound messages. The component responsible for this check is the transport agent, which enforces message size limits to prevent abuse and ensure efficient mail delivery. This error can occur due to various reasons such as oversized attachments, large message bodies, or misconfigured mail flow rules that enforce a lower limit than the default maximum allowed by Exchange Online. Understanding these nuances is crucial for troubleshooting and resolving issues related to this error code effectively.Affected Versions and Scope
This error affects all versions of Microsoft 365 / Exchange Online where message size limits are enforced. The scope includes both on-premises hybrid environments that connect to Exchange Online as well as pure cloud-based deployments. It is important to note that this issue does not affect standalone on-premises Exchange servers unless they are configured in a hybrid environment with Exchange Online. The default maximum message size for Exchange Online is 25 MB, but administrators can increase it up to 150 MB per mailbox or connector. However, if the hybrid on-premises connector has a lower MaxMessageSize setting than what is allowed by Exchange Online, messages will still be rejected based on the lower limit.Where To Look First: Logs and Event IDs
To diagnose this issue, you should first examine the logs generated by Exchange Online. The relevant log files are located at:C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceLogs\HealthService.log(for on-premises hybrid environments)/var/log/exchange/MessageTracking(for cloud-based Exchange Online deployments)
Get-MessageTrackingLog to retrieve detailed information about failed messages. Look for log entries with a status of "Failed" and reason 'MessageTooLarge'. For example:
Get-MessageTrackingLog -ResultSize Unlimited | Where-Object {$_.Reason -eq "MessageTooLarge"}
Additionally, you can check the Exchange admin center (EAC) for message trace information. Navigate to EAC > Mail flow > Message trace, and filter by failed messages with a reason of 'MessageTooLarge'. This will provide insights into which specific messages are failing due to size limitations.
Root Causes
There are several distinct causes that can trigger the "552 5.3.4" error code:1. Oversized Attachments or Message Body
When an email message exceeds the maximum allowed size, either due to large attachments or a lengthy message body, Exchange Online will reject it with this error code. To differentiate this cause from others, check if the offending messages contain unusually large files or extensive text content that could surpass the configured limits. You can also use PowerShell cmdlets likeGet-TransportRule to inspect any rules that might be affecting message size:
Get-TransportRule | Where-Object {$_.State -eq "Enabled"}
2. Misconfigured Mail Flow Rules
Mail flow rules can enforce stricter limits on message sizes than the default Exchange Online settings. If a rule is set to reject messages larger than 25 MB, for example, it will override any higher limit configured in the mailbox or connector settings. To identify if this is the cause, review your mail flow rules and check their size restrictions using:Get-TransportRule | Where-Object {$_.State -eq "Enabled"} | Select-Object Name,SizeRestriction
3. Hybrid On-Premises Connector Limitations
In hybrid environments where on-premises Exchange servers connect to Exchange Online, the maximum message size can be limited by the settings of the hybrid connector. If this limit is lower than what Exchange Online allows, messages will fail with the "552 5.3.4" error. To verify if this is the issue, check the MaxMessageSize setting on your hybrid connectors:Get-RemoteDomain | Select-Object DomainName,SmtpRejectMessagesFromGroups
Adjust these settings to match or exceed the limits allowed by Exchange Online.
Fix Procedure
To resolve this issue, follow these steps: 1. **Increase Message Size Limits**: Use the Exchange admin center (EAC) > Mail flow > Rules/Connectors/Accepted domains to adjust message size limits for your organization or specific mailboxes. Alternatively, use PowerShell cmdlets likeSet-TransportConfig and Set-Mailbox:
Set-TransportConfig -MaxSendSize 30MB -MaxReceiveSize 30MB
Set-Mailbox -Identity -MaxSendSize 30MB -MaxReceiveSize 30MB
2. **Adjust Mail Flow Rules**: Review and modify any transport rules that enforce size restrictions lower than the desired maximum message size:
Get-TransportRule | Where-Object {$_.State -eq "Enabled"} | Select-Object Name,SizeRestriction
Set-TransportRule -Identity -SizeRestriction 30MB
3. **Update Hybrid Connectors**: Ensure that hybrid connectors have the same or higher MaxMessageSize settings as Exchange Online:
Get-RemoteDomain | Select-Object DomainName,SmtpRejectMessagesFromGroups
Set-RemoteDomain -Identity -MaxMessageSize 30MB
4. **Advise Senders**: Inform users to use OneDrive or SharePoint links for large files instead of attaching them directly.
Note: Be cautious when modifying registry keys, as incorrect changes can break enrolled devices.
A quick diagnostic shortcut is to run
Get-MessageTrackingLog -ResultSize Unlimited | Where-Object {$_.Reason -eq "MessageTooLarge"} | Select-Object Sender,Recipient,Subject,BytesSent in PowerShell to quickly identify problematic messages.
Error Code Variants
| Error Code | Description | Distinguishing Features |
|---|---|---|
| 550 5.3.4 | Generic error indicating a problem with the message or recipient. | This code is less specific and does not indicate a size-related issue. |
| 552 5.1.7 | Error related to exceeding the maximum number of recipients per message. | Distinguished by the recipient limit rather than the message or attachment size. |
Verification
After implementing changes, verify that the issue is resolved by checking for successful delivery in the logs and EAC. Look for log entries with a status of "Delivered" instead of "Failed". Additionally, confirm that new messages are not being rejected due to size limitations. You can also use PowerShell cmdlets likeGet-MessageTrackingLog to monitor message flow:
Get-MessageTrackingLog -StartDate (Get-Date).AddHours(-2) -EndDate (Get-Date)