About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The bounce "Remote server returned '550 5.2.3 RESOLVER.RST.RecipSizeLimit;message too large for this recipient'" means the message is larger than the receiving mailbox accepts. The limit that matters is the recipient's MaxReceiveSize, the sender's MaxSendSize, and the extra size that encoding adds to an attachment, not the size of the file on disk.
Read both mailboxes' current limits first. Then change one mailbox, with the old values written down, and test again.
What the error means
Microsoft's page on message size limits gives the message you receive when a recipient's limit is the cause: "Remote server returned '550 5.2.3 RESOLVER.RST.RecipSizeLimit;message too large for this recipient'".
Microsoft's numbers on the same page: by default the maximum message size is 35 MB for sending and 36 MB for receiving. Administrators can set mailbox-specific limits up to 150 MB, from 1 MB through 150 MB. The page stresses: "The message size limit isn't the same as the attachment size limit." The total message size "includes the message body, headers, attachments, and any extra size introduced by encoding or content conversion."
The page says Base64 encoding "can increase the size of binary data by approximately 33 percent", and that a mailbox configured at 150 MB does not mean every 150 MB attachment can be sent. Messages that stay inside Microsoft datacentres can be up to 150 MB, subject to the mailbox, client and service limits. Messages routed outside them take a further 33 percent translation increase, so Microsoft documents 112 MB as the maximum for those.
The client matters too. The page says Outlook supports messages up to the applicable maximum, while "Outlook on the web accounts for possible encoding expansion and can restrict the message size to approximately 25% less than the configured mailbox limit".
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
Recipient's MaxReceiveSize is below the message size |
550 5.2.3 RESOLVER.RST.RecipSizeLimit | Read the recipient mailbox's MaxReceiveSize |
Sender's MaxSendSize is below the message size |
Message refused; Microsoft says to check the sender's limit | Read the sender mailbox's MaxSendSize |
| Encoding pushes the message over a limit | A file that looks smaller than the limit still fails | Add about 33 percent to the attachment size and compare |
| Message leaves Microsoft datacentres | Works to a colleague, fails to an outside address | Microsoft documents 112 MB as the maximum for messages routed outside |
| Outlook on the web used instead of Outlook | Same file sends from Outlook but not from the web | Microsoft says the web client can restrict to about 25 percent below the limit |
| The recipient's own provider has a smaller limit | The bounce comes from a remote server | Microsoft says an outside recipient's provider might enforce a smaller limit |
| Hybrid or gateways in the path | Failure on one route only | Microsoft says to consider on-premises servers, connectors and third-party gateways |
Microsoft's page does not rank these causes. It says "the lowest applicable limit anywhere in the mail path can determine whether the message is delivered."
Prove the cause before changing anything
All of these read only. They need Exchange Online PowerShell. The Connect-ExchangeOnline page documents how to connect:
Connect-ExchangeOnline -UserPrincipalName <admin@contoso.com.au>
Then read the limits of the recipient and of the sender. The Get-Mailbox page documents -Identity and Format-List shows the chosen properties:
Get-Mailbox -Identity <recipient@contoso.com.au> | Format-List Name,MaxSendSize,MaxReceiveSize
Get-Mailbox -Identity <sender@contoso.com.au> | Format-List Name,MaxSendSize,MaxReceiveSize
Write down the four values by copying the output into the ticket. Also note which client sent the message (Outlook, Outlook on the web or another client), and whether the recipient is inside your organisation, in another Microsoft 365 tenant or outside.
Example (illustrative): at contoso.com.au a user on rds01 attaches a 100 MB drawing file and sends it to a customer at an outside address. With encoding the message is about 100 MB + 33 percent (33 MB) = 133 MB. The user's MaxSendSize shows 150 MB, and 133 MB is below that. Leaving Microsoft's datacentres adds Microsoft's "additional 33 percent translation encoding increase", which is why Microsoft gives 112 MB as the maximum for messages routed outside. 133 MB is above that 112 MB, so the message can fail even though the file is under 150 MB. Sending the same file to a colleague inside the tenant stays within Microsoft's datacentres, where up to 150 MB is allowed, and 133 MB is below that, but it only works if the colleague's MaxReceiveSize is also high enough; the default is 36 MB. The right answer for the customer is a link, not a larger limit.
Fix
A better option for very large files
Microsoft's page says: "Increasing the email message size limit isn't always the best solution." It suggests storing the files in OneDrive or SharePoint and sharing a link, because that reduces the size of the email message and avoids the extra size added when attachments are encoded. The sections below apply when a bigger message is genuinely needed.
Raise the limit on one mailbox
Microsoft's example sets both values to 75 MB with Set-Mailbox. The Set-Mailbox page says to qualify values with a unit such as MB, that in Exchange Online you "can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license", and that because Base64 adds about 33 percent you should specify a value 33 percent larger than the message size you want to allow. Its example: the value 64 MB results in a maximum message size of approximately 48 MB.
Before you change the mailbox, record its current limits by running this read-only command for it, and keep the output with the ticket:
Get-Mailbox -Identity <recipient@contoso.com.au> | Format-List Name,MaxSendSize,MaxReceiveSize
Risk: The next command changes the maximum message size the named mailbox can send and receive. A bigger limit lets larger messages through to that mailbox. Microsoft's limits page says message size limits exist to prevent large messages from blocking delivery of other messages and affecting service performance for all users. The change applies to that mailbox only; it does not change any other mailbox or the mailbox plan.
Set-Mailbox -Identity <recipient@contoso.com.au> -MaxSendSize 75MB -MaxReceiveSize 75MB
If the sender's limit is the low one, use the sender's address in the same command, with the sender's record taken the same way. Microsoft's page says to allow up to 30 minutes after the update process is finished before testing the new settings.
To undo it: run the same cmdlet with the values you recorded, for example, if the record shows 35 MB and 36 MB:
Set-Mailbox -Identity <recipient@contoso.com.au> -MaxSendSize 35MB -MaxReceiveSize 36MB
Mailboxes created in future
Microsoft's page says Set-MailboxPlan with -MaxSendSize and -MaxReceiveSize updates the defaults for mailboxes created in future, and its page for Set-Mailbox says the plan cmdlet is the way to change those values for new mailboxes. That change affects every new mailbox, and Microsoft's page gives no back-out for it, so no steps are given for it. Microsoft's Get-MailboxPlan page shows Get-MailboxPlan -Identity <plan name> | Format-List; read the plan's size properties that way, keep the output, and decide with the business owner before you change a plan.
The recipient is outside your organisation
Nothing in your tenant can raise a limit that belongs to the recipient's provider. Microsoft says the recipient's provider "might enforce a smaller message size limit." Ask the recipient to confirm their limit, or send a link.
Confirm the fix
- Wait the time Microsoft gives, then send a test message of the size you need, from the same client, to the same recipient.
- Run the two
Get-Mailboxcommands again and check the values are the ones you set. - If it still bounces, check the other items in Microsoft's list: the sender's limit, the client, the destination, encoding, outside limits and other systems in the mail path.
What to watch afterwards
- Mailbox size growth on any mailbox with a raised limit.
- Messages that fail only from Outlook on the web. Microsoft says it can restrict to about 25 percent below the configured limit.
- Distribution groups: Microsoft's limits page lists a separate maximum message size for groups with 5,000 or more recipients, and says a message above it is not delivered and the sender gets an NDR.
Read next
Related articles you may want next.
- TroubleshootingExchange Online 550 5.7.124 "Sender not in allowed-senders list": a sender is blocked from a group550 5.7.124 Sender not in allowed-senders list: add the sender to the group's list or lift the restriction. Steps with a way back.Read article
- TroubleshootingExchange Online 5.1.90 "Your message can't be sent because you've reached your daily limit for message recipients"5.1.90 daily limit for message recipients in Exchange Online: the 10,000 limit, how it is counted, what to check and what cannot be raised.Read article
- TroubleshootingExchange Online '554 5.2.2 mailbox full' when sending to a mail-enabled public folder554 5.2.2 mailbox full on a mail-enabled public folder? Check the folder, organisation and public folder mailbox quotas, then raise only the one reached.Read article
Risks and limits
These commands have not been run or lab-tested.
Microsoft's size-limit page names Exchange Online and gives the limits as of its date. The limits page table shows a 150 MB message size limit for Outlook and 112 MB for Outlook on the web in its plan columns, with footnotes attached to those figures, so check the current page before you quote a figure to a customer. Microsoft's cmdlet reference pages show no update date. The figures in the example are illustrative. The cmdlets above change one mailbox; the page's commands that update all mailboxes at once cannot be reversed from a single record.
Sources
- Message size limits in Exchange Online — Microsoft Learn, page dated 2026-11-03, accessed 22 November 2026
- Exchange Online limits — Microsoft Learn, page dated 2026-11-11, accessed 22 November 2026
- Set-Mailbox — Microsoft Learn, date not shown, accessed 22 November 2026
- Get-Mailbox — Microsoft Learn, date not shown, accessed 22 November 2026
- Get-MailboxPlan — Microsoft Learn, date not shown, accessed 22 November 2026
- Format-List — Microsoft Learn, date not shown, accessed 22 November 2026
- Connect to Exchange Online PowerShell — Microsoft Learn, page dated 2025-07-11, accessed 22 November 2026
This article was originally published on .