Fix it now
The message was bigger than a size limit somewhere on its path. There are four independent limits stacked on top of one another, any of them can reject it, and Microsoft’s rule is simple: the most restrictive limit is enforced. The job is to find the smallest one, not to raise all four.
Get-TransportConfig | Format-List MaxSendSize,MaxReceiveSize
Get-SendConnector | Format-List Name,MaxMessageSize
Get-ReceiveConnector | Format-List Identity,MaxMessageSize
Get-Mailbox sender@contoso.com | Format-List MaxSendSize,MaxReceiveSize
- Note the size on the wire, not the size of the attachment. Base64 encoding adds roughly 33%, so Microsoft’s own worked example is that a 64 MB limit allows a realistic message of about 48 MB.
- Compare your four numbers against the documented defaults: 10 MB for the organisation send and receive, 36 MB on a receive connector, 10 MB on a send connector, and Unlimited on a mailbox.
- Identify which connector the failing message actually used, from the message tracking log rather than by guessing.
- Raise only the smallest limit in that path, for example
Set-SendConnector 'To Internet' -MaxMessageSize 35MB. - Retest with a message of a known size before you tell the user it is fixed.
Mailbox size limits are checked before mail flow rules are evaluated, so a mailbox limit can pre-empt the rule you are staring at.
If a message of the size the user needs now goes through end to end, you are done. If the rejection names somebody else’s server, the next section explains why you cannot fix that one.
Why it happens
Exchange applies a size limit at each stage a message passes through, and Microsoft’s stated order of precedence is that the most restrictive limit is enforced. The organisation-wide transport configuration sets a default for everything, and its documented default is 10 MB for both send and receive. Each send and receive connector carries its own limit, defaulting to 10 MB and 36 MB respectively. Each mailbox has its own send and receive limits, which default to Unlimited and override the organisation values for that person when they are set. Mail flow rules can add a further restriction based on size.
There is one documented exception to the precedence rule and it is worth knowing before you start disabling rules to test: Exchange checks the maximum message size allowed on mailboxes before mail flow rules process the message. Microsoft’s own example has a 50 MB organisation limit, a 35 MB mailbox limit and a rule rejecting anything over 40 MB – a 45 MB message is rejected by the mailbox limit before the rule ever sees it.
The other thing that catches people is encoding. Attachments are not sent as raw bytes; they are encoded into a text-safe form, and Microsoft states that Base64 encoding increases the size of the message by approximately 33%, so any limit should be set about a third higher than the real message size you want to allow. A 25 MB limit does not allow a 25 MB attachment, and the same margin has to exist on every limit in the path, not only the one you edited.
Some limits are not in transport at all. Outlook on the web, Exchange ActiveSync and Exchange Web Services each carry their own, configured in web.config on the Mailbox server rather than in the admin centre. A message that never reaches the tracking log was stopped by one of those, or by the client itself.
A connector is set lower than the organisation limit
You have this one if The organisation values look generous but mail across one path bounces at a smaller size.
- List every connector with its limit and compare against the documented defaults – 10 MB on a send connector is a default, not somebody’s decision.
- Identify the connector the failing message actually used, from the tracking log.
- Raise only that connector:
Set-SendConnector 'To Internet' -MaxMessageSize 35MB - Confirm the change landed on the right one; organisations often have more than one internet-facing connector.
The mailbox carries its own limit
You have this one if One user cannot send or receive large messages while colleagues on the same server can.
- Check the mailbox:
Get-Mailbox user | Format-List MaxSendSize,MaxReceiveSize. A value here overrides the organisation default for that person. - Clear the override with
Set-Mailbox user -MaxSendSize Unlimited -MaxReceiveSize Unlimited; Unlimited at mailbox level still leaves the organisation and connector limits in force. - If the limit was deliberate, set an explicit larger value rather than removing it.
- Remember the ordering: this limit is applied before any mail flow rule.
Mailbox-level limits are often stamped by a provisioning script or a mailbox plan and reappear the next time the user is reprovisioned. Fix the template as well as the mailbox.
The receiving organisation is the one refusing
You have this one if Your logs show the message left cleanly and the rejection text names their server.
- Read the reporting server name in the non-delivery report. If it is not yours, the limit is theirs.
- Ask them for their maximum inbound size and send within it.
- Send a link to a file share instead. For anything genuinely large this is the answer, because no realistic mail limit accommodates modern file sizes.
A mail flow rule is enforcing a size condition
You have this one if Messages bounce only when they match some other characteristic as well as being large – a particular recipient, or an attachment type.
- List rules with size conditions and read the whole rule before changing it. Size conditions are often part of a data protection control rather than a performance one.
- Remember that a mailbox size limit is evaluated first, so a rule you suspect may never have been reached.
- Adjust the threshold or narrow the rule’s scope if the restriction is no longer wanted.
- Re-enable anything you disabled for testing before you finish.
The client refused before transport ever saw it
You have this one if The failure happens at send time in the client, or an upload stalls in the browser, and nothing appears in the tracking log.
- Check whether the message exists in the tracking log at all. If it does not, none of the transport limits are relevant.
- Have the user retry from a different client, which separates a client limit from a server one.
Full reference
The documented defaults, so you can tell a default from a decision
| Limit | Cmdlet and parameter | Default |
|---|---|---|
| Organisation maximum receive size | Set-TransportConfig -MaxReceiveSize |
10 MB |
| Organisation maximum send size | Set-TransportConfig -MaxSendSize |
10 MB |
| Receive connector maximum message size | Set-ReceiveConnector -MaxMessageSize |
36 MB |
| Send connector maximum message size | Set-SendConnector -MaxMessageSize |
10 MB |
| Mailbox maximum send size | Set-Mailbox -MaxSendSize |
Unlimited |
| Mailbox maximum receive size | Set-Mailbox -MaxReceiveSize |
Unlimited |
| Active Directory site link | Set-AdSiteLink -MaxMessageSize |
Unlimited |
Client limits, which live somewhere else entirely
| Client | Default | Where it is configured |
|---|---|---|
| Outlook on the web | 35 MB | web.config on the Mailbox server |
| Exchange ActiveSync | 10 MB | web.config on the Mailbox server |
| Exchange Web Services | 64 MB | web.config on the Mailbox server |
None of these are available in the Exchange admin centre, which is why a size that transport accepts can still be refused in a browser. If a user can send a file from Outlook and not from Outlook on the web, this table is where to look.
Reading the bounce to locate the limit
| Where the message failed | Limit to check first |
|---|---|
| Internal mail works, external mail bounces | The send connector to the internet, which defaults to 10 MB |
| One sender bounces, others do not | That sender’s mailbox MaxSendSize |
| Inbound mail from one partner bounces | Your receive connector for that path, then the organisation receive limit |
| The far end refuses it | Their limits, not yours |
| Everything above a size bounces everywhere | The organisation transport configuration |
| Only messages matching a pattern bounce | A mail flow rule with a size condition |
| Nothing appears in the tracking log at all | A client limit, in web.config or in the client itself |
Setting a limit that will hold
- Decide the largest file your users genuinely need to send.
- Add about a third for encoding overhead. Microsoft’s worked example is a 64 MB limit yielding a realistic maximum of roughly 48 MB.
- Set the organisation limit to that figure and make every connector and mailbox limit in the path equal or larger.
- Keep the limits the same in all locations, or configure the more restrictive ones where messages enter the organisation – that is Microsoft’s stated recommendation, and it avoids processing a message you are going to reject anyway.
- Test with a message of the target size before you tell anyone it is done.
The codes in this group
| Code | Class definition | Source |
|---|---|---|
| 552 5.3.4 | The message is larger than the per-message size limit, for physical or administrative reasons | RFC 3463; not published by Microsoft |
| 550 5.2.3 | A per-mailbox administrative message length limit has been exceeded, used when that limit is smaller than the general system limit | RFC 3463; not published by Microsoft |
| 550 5.3.4 | The same per-message size class, with a permanent 550 prefix | RFC 3463; not published by Microsoft |
The distinction between the two classes is genuinely useful. 5.2.3 is the mailbox’s own limit, so it points at MaxSendSize or MaxReceiveSize on one recipient or sender. 5.3.4 is a system limit, so it points at the organisation configuration or a connector. Neither is published by Microsoft with Exchange-specific wording, so read the reporting server name in the bounce and the four numbers above rather than the code alone.
Very large limits are not free. They move the cost into queue storage, backup windows and mailbox growth, and most external recipients will refuse the message anyway – the receiving organisation applies its own limits after yours. Set the limit to what people actually need and use a file share for the rest.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
552 5.3.4 |
The message is larger than the per-message size limit. Not published by Microsoft; this is the RFC 3463 class definition | RFC 3463 |
550 5.2.3 |
A per-mailbox administrative message length limit was exceeded, used when it is smaller than the general system limit. Not published by Microsoft | RFC 3463 |
550 5.3.4 |
The same per-message size class reported permanently. Not published by Microsoft | RFC 3463 |
Confirm the fix worked
- A test message at the target size is delivered end to end and shows a DELIVER event in the tracking log.
Get-TransportConfig, the relevant connectors and the affected mailboxes all report limits consistent with that size plus about a third for encoding.- A message deliberately above the new limit is still rejected, which proves the limit in force is the one you set.
- External recipients confirm receipt, since your outbound limit is only half of the path.
- Any rule you disabled while testing is enabled again.
Questions people ask about this
Does fixing this cost anything?
No. Every limit involved is a configuration value you already own. There is no licence or add-on that raises a message size limit, and nobody should be selling you one.
What is a sensible maximum to set?
The largest file your users genuinely need to send, plus about a third for encoding overhead, and no more. Microsoft’s own example is that a 64 MB limit yields a realistic maximum of about 48 MB.
Why does the same file work to one recipient and not another?
Because the receiving side applies its own limits after yours. You control the smallest limit on your side of the path only.
Do I need to restart anything after changing a limit?
Connector and organisation changes take effect for new messages without a restart, though it can take a few minutes for transport to pick the configuration up from the directory. A message that already bounced will not be retried; it has to be sent again.
I disabled the rule with the size condition and it still bounces. Why?
Because mailbox size limits are evaluated before mail flow rules. If the mailbox limit is the smallest number in the path, the rule was never reached.
