Set Message Size Limits in Exchange 2010 and Exchange 2007

by Bharat Suneja

In Distribution Groups and maximum recipients per message, we looked at how the maximum recipients per message settings are treated differently by Exchange Server 2010/2007 and Exchange 2003/2000 when sending to Distribution Groups.

Message size limits are an important mechanism to control mailbox sizes, guarantee service availability, and protect from potential DoS attacks. Another commonly asked question is about message size limits and the inability to send messages that are apparently within the maximum sizes configured. Let’s take a look at the message size settings in different places in Exchange 2010 and Exchange 2007.

1Organizational limits

The organizational send and receive size limits apply to all Exchange servers in the Organization. The default is 10MB.

You can modify the organizational message size limits using the Set-TransportConfig cmdlet from the Exchange shell:

Set-TransportConfig -MaxReceiveSize 40MB -MaxSendSize 40MB

In Exchange 2007 SP1 and later, you can also set the organizational message size limits using the EMC by going to Organization Configuration | Hub Transport | Global Settings tab | Transport Settings | properties | General tab.

Exchange Server 2007 | Transport Settings
Figure 1: Setting the organizational message size limits from the Global Settings tab in the EMC in Exchange 2007 SP1 and later

2Receive Connector limit

Unlike Exchange SMTP Virtual Servers in Exchange Server 2003/2000, Exchange 2007’s Receive Connectors are only used to receive messages. You can use different Receive Connectors with different maximum message size limits. For example, a Receive Connector for inbound Internet mail may have lower message size limits, but you may want to allow larger messages on Receive Connector for authenticated senders, partners or scanners and multi-function devices that can send large scanned images or PDF files.

To modify the maximum message size on a Receive Connector using the Exchange console, select Server Configuration | Hub Transport | select a Hub Transport server | Receive Connectors -> select a connector | Properties | General tab.

Screenshot: Maximum message size on a Receive Connector
Figure 2: Setting the maximum message size on a Receive Connector

To set ReceiveConnector limit using the shell:

Set-ReceiveConnector “CONNECTOR NAME” -MaxMessageSize 40Mb

What’s a Unique Binding for a Receive Connector?

Exchange 2003/2000’s SMTP Virtual Servers consider a unique combination of an IP address + TCP port number as a unique binding, and don’t allow another SMTP Virtual Server to be bound to the same IP address + port combination. Exchange 2010/2007’s more evolved view of a unique binding is a combination of IP address + port + RemoteIPRanges.

What this means:

  • You don’t need another IP address to create a separate Receive Connector with different settings.
  • You don’t have to use a non-default port when using the same IP address to create a separate Receive Connector.
  • You can create a Receive Connector using the same IP address + port number, but using different RemoteIPRanges to specify the remote hosts that can connect to it. For example, you can create a Receive Connector for a set of remote hosts and specify a different message size to allow those hosts to send larger messages, or to restrict them to smaller messages.

3 Send Connector limit

Send Connectors are used for sending outbound messages to the internet or particular address spaces (domains). Edge Transport servers also have a Send Connector to send inbound messages to Hub Transport servers in an AD Site. To modify the maximum message size on Send Connectors, select Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties | General tab.

Screenshot: Maximum message size on a Send Connector
Figure 3: Setting the maximum message size on a Send Connector

To set SendConnector limit using the shell:

Set-SendConnector “CONNECTOR NAME” -MaxMessageSize 40Mb

4 Recipient limits

In Exchange 2010/2007, you can configure individual message size limits on the following recipient types to bypass the Organizational limits:

  • Mailbox (Mailbox User, aka mailbox-enabled user in previous versions)
  • Contact (aka Mail Contact)
  • Mail User (aka mail-enabled user in previous versions)
  • Distribution Group
  • Public Folder

To set these using the Exchange console: Recipients | Mailbox -> select mailbox (or select another recipient type such as a contact or mail user from the corresponding node) | properties | Mail Flow Settings tab | Message Size Restrictions.

Figure 4: Setting the maximum message size on a mailbox

To set message size limits on a mailbox using the Exchange shell:

Set-Mailbox “Joe Adams” -MaxSendSize 20Mb -MaxReceiveSize 20Mb

Distribution Groups and Contacts (MailContacts) only have maximum receive size in the Exchange console, but both MaxReceiveSize and MaxSendSize properties can be set for them using the Exchange shell.

Do individual message size limits bypass the Organization message size limits?

This is perhaps one of the most misunderstood part of message size limits, and therefore a frequently asked question: when you specify individual message size limits for a recipient, does it override other message size limits in your Exchange organization?

In a nutshell, setting higher message size limits on an Exchange recipient bypasses the maximum message sizes in the Exchange Organization configuration, but only for internal messages, not for messages sent to or received from the Internet and other unauthenticated sources.

Remember, for a message to be delivered successfully, the message size must be within the max message size limits applicable to both – the sender and the recipient. Because the identity of unauthenticated or anonymous senders and recipients can’t be established (because… they’re unauthenticated!), the organizational limit applies.

5 Active Directory SiteLink limit

In Exchange Server 2007 SP1, you can also set maximum message size limit on AD Site Links. Exchange Server 2007 uses the AD Site topology to determine the least cost paths. If the message size to be delivered to a remote AD Site exceeds the limit on the AD Site Link, message delivery will fail. By default, the MaxMessageSize on AD Site Links is set to unlimited. This can be changed using the following command:

Set-ADSiteLink “SITE LINK NAME” -MaxMessageSize 20Mb

Message size limits during coexistence with Exchange 2003

Global Settings

Besides the above, another message size limit can impact Exchange Server 2010/2007 recipients if you’re transitioning from Exchange 2003/2000, but it’s often overlooked when troubleshooting. This is the one in Exchange Server 2003 Global Settings | Message Delivery -> Properties.

Screenshot: Using ADSIEdit to configure message sizes and max recipients per message in Global Settings
Figure 5: You can use ADSIEdit to configure message size and max recipients per message in Global Settings

If you have these configured to a specific value before you upgrade the Organization to Exchange Server 2010/2007, these are left untouched.
If you have these set to “No Limit” before the Exchange Server 2007 upgrade, these are reset to the Exchange Server 2007 defaults.
– In case Exchange Server 2007’s Organization settings (the ones you can set using Set-TransportConfig) conflict with these legacy Global Settings, the lower of the two sizes are used.

The problem is, these are neither visible in the EMC, nor using any of the Exchange shell commands.

If you still have an Exchange Server 2003 server in the Organization, you can use ESM to modify these limits. Alternatively, you can use ADSIEdit to browse to the Configuration container | Services | Microsoft Exchange | YourOrgName | Global Settings | Message Delivery -> Properties, and modify the following attributes as required:

  1. delivContentLength -> corresponds to MaxReceiveSize parameter in Set-TransportConfig command.
  2. SubmissionContentLength -> corresponds to MaxSendSize parameter in Set-TransportConfig command.

    Note: The maximum value for both of the above is 2097151 KB, slightly under 2 Gb.

  3. msExchRecipLimit -> corresponds to MaxRecipientEnvelopeLimit parameter in Set-TransportConfig command.

Set these to be the same as the equivalent Organization settings in Exchange Server 2007.

Exchange Server 2007 SP1 makes managing changes to Exchange 2003’s Global Settings easier— if they have numeric values (i.e. aren’t set to “No Limit”), using Set-TransportConfig to change maxReceiveSize, maxSendSize or maxRecipientEnvelopeLimit also changes the corresponding Global Settings.

Routing Group Connector Limit

Routing Group Connectors are used in co-existence scenarios to transfer messages between Exchange Server 2003/2000 Routing Groups and the Exchange Server 2007 Routing Group (yes, there is one under the hood.. ). Messages exchanged between these Routing Groups should be below the message size limits of their respective RGCs. The default is set to unlimited.

To set the MaxMessageSize on a Routing Group Connector:

Set-RoutingGroupConnector “CONNECTOR NAME” -MaxMessageSize 20Mb

Content conversion and message size limits

When troubleshooting message size-related issues, the content conversion process was another source of confusion. Content conversion happens when Exchange converts an internet/MIME message to MAPI/Exchange format, and vice versa. Content conversion generally increases the message size — roughly by 30%. If you set a maximum message size of 10Mb., and wonder why a 9 Mb. attachment didn’t make it through, consider the content conversion overhead, as also message headers (which are computed along with the DATA portion of the message to calculate the message size), and any actions taken by Transport Rules or other transport agents.

How does Exchange 2010/2007 handle such messages? When a message enters the Exchange 2010/2007 Organization, it gets stamped with a X-MS-Exchange-Organization-OriginalSize header, which indicates the original size of the message before content conversion. When considering message size limits, if the message has since ballooned to a larger size due to content conversion, added headers, etc. the lower of the original message size and the current (converted) message size is considered, eliminating some of the confusion seen with message sizes in previous versions.

Troubleshooting Sender and Recipient Size Limits

Consider the sender’s MaxSendSize and the internal recipient’s MaxReceiveSize when troubleshooting message size issues.

If the the sender isn’t allowed to send a message of that size, you get the following NDR:

#550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this sender ##

If the sender’s size limits allow sending a large message, but the recipient’s limits do not allow receiving a message of that size, you get a NDR with the following text (note the enhanced status code informing you exactly why the message was rejected):

#550 5.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient ##

Using the Exchange shell to track failed message delivery

You can use the Exchange shell to track messages that could not be delivered because of message size issues. The RecipientStatus field in Message Tracking logs is used to store the SMTP response and enhanced status codes. The Message Tracking EventID we’re looking for is FAIL. (Read previous post on message tracking: “Exchange Server 2007: Message Tracking from the command line“)

To track messages that failed because of recipient’s MaxReceiveSize:

Get-MessageTrackingLog -EventID FAIL | where {$_.RecipientStatus -like “*RecipSizeLimit*”}

To track messages that failed because of the sender’s MaxSendSize:

Get-MessageTrackingLog -EventID FAIL | where {$_.RecipientStatus -like “*SendSizeLimit*”}

Exchange MVP Michel de Rooij has published a Configure-ClientSizeLimits.ps1 script to allow you to configure message size limits affecting OWA and EAS clients. See Client Message Size Limits on his blog.

Message size limits in Exchange Online

In Exchange Online, the message size limit is set to 150MB (for Outlook on Windows, 112MB for OWA and a much lower 35MB for Outlook Mac – likely Outlook Mac 2011). Exchange Online also limits the number of attachments per message to 250. You can find all Exchange Online limits, including message size limits, in a single, comprehensive doc – Exchange Online Limits.

Message size-related documentation

{ 119 comments… read them below or add one }

KHUNCUNG November 20, 2010 at 6:54 pm

I Love U…..


dglenn November 23, 2010 at 9:03 am

Thank you, thank you, thank you, the information was extremly helpful.


Steve Einhorn November 29, 2010 at 8:25 am

Does anything need to be restarted in EX 2010 after changing the size restrictions on a users mailbox ????



Bharat Suneja December 5, 2010 at 7:57 pm

No, you won’t need to restart anything, although the changes may not kick in immediately. See Mailbox Size Limits Are Not Enforced in a Reasonable Period of Time.


Massimo August 6, 2014 at 5:21 am

Great!!!! very usefull, restarting the “Microsoft Exchange Information Store service” on the BE (as is written in the article you suggested), the modification take place immediatly :)


Jane Yang December 8, 2010 at 1:35 pm

Very useful. Thanks a lot for your contribution!!!


Bharat Suneja December 9, 2010 at 6:36 am

Thx for the feedback! :)


SeemonRaj S December 30, 2010 at 3:40 pm


Excellent job!!!

Thank you,


aryx February 7, 2011 at 3:11 pm

Hi, how would you configure a lower limit for attachment sent inside the exchange organization and a larger limit when sending out to external users?


Bharat Suneja February 7, 2011 at 4:06 pm

There are no separate limits for inside org and messages received from outside. The organization limit should be the largest message size you want to allow (in this case, to/from external users). You can have a lower limit on Receive Connectors which receive inbound Internet email, but not the other way round.


Viren March 16, 2011 at 11:00 pm

Excellent! Thanks


David March 20, 2011 at 8:33 pm

Love the article. Very clear and concise.

Just one request for clarification, though. With the Organizational limits, the function of “Transport Dumpster” has changed between Exchange 2007 and 2010. Factoring in these changes, does changing the other transport (send and receive) maximum sizes influence what you would set for the “Maximum size per mailbox database (MB)”? Thanks…


ANDREY FYODOROV April 27, 2011 at 6:20 am

I think Microsoft dropped a ball with this design.

Consider this situation:

Global Send limit – 10MB
Global Receive limit – 20MB
Certain VIP users have Send/Receive limits set at 20MB.

So the VIPs should be able to Receive, say, a 15MB message from the Internet just fine, right? WRONG!

One would think that Exchange would use the Global RECEIVE limit to evaluate incoming messages from the Internet.
BUT NO, Exchange uses the Global SEND limit for INCOMING mail. What kind of messed up logic is this?
I have never seen any other mail server that could not tell the difference between Incoming and Outgoing mail [and apply policies accordingly]

Add insult to injury. When 10MB SEND limit is set, Exchange cannot even receive 10MB messages because of the content conversion bloat.
So you say, big deal, increase the send limit to ~14MB, problem solved, right?
If I set the send limit to 14MB, I will be able to receive 10MB messages from the Internet allright…

But then my own users will be able to literally send 14MB messages out. I tell them the limit is 10MB, they will tell me I am a liar because they are sending 14MB out all day long.


Obeid Mirza June 30, 2011 at 9:57 am

I have the exact same problem!! and yes they called me a liar too….


GiangDC April 14, 2012 at 12:04 am

Hi, I’ve met the same situations as you two and like ANDREY FYODOROV said I had to increase the SEND limit – (Not the RECEIVE) in order to receive a larger mail.

It’s ~ one year since this thread posted , so do Microsoft patch this bug ? or do you guys have any solution for this ?


Bharat Suneja November 20, 2012 at 11:51 am

Microsoft doesn’t monitor this blog. You can submit Exchange feature ideas and feedback to the Exchange team at exwish at microsoft.


Alex Mack November 16, 2012 at 1:04 pm

Thank you Andrey. I spent hours today trying to figure out why my stupid Exchange server was still not receiving attachments of more than 10MB even though I changed it. Extremely dumb by Microsoft.


טכנאי מחשבים | תיקון מחשבים May 21, 2011 at 6:06 am

thanks a lot find it very helpfull


Gurdip May 22, 2011 at 6:28 pm

Thanks buddy….you saved me!!!


Randeep July 20, 2011 at 2:19 am

Hi Bharat,

We have two sets of users: Standard users and VIP users.
We want standard users to be able to send mail externally with a limit of 10MB and for VIP users to be able to send mail externally with a limit of 15MB.

We have only one Internet Send Connector. How do we configure Exchange to allow the two sets of users to send mail externally with their limits?

I know we can edit the ‘Message Size Restrictions’ on the inividual mailbox properties, but that is only for internal messages as you stated above.
How do we set this for external users?

Thanks in Advance


Bharat Suneja July 20, 2011 at 8:41 am

You can’t do this using message size limits. For a message to be successfully sent and received, it must be within the size limits of the sender *and* the recipient. As noted in the post, messages sent/received to/from Internet senders are considered as sent/received by anonymous senders.

Another option would be transport rules, but there’s no predicate to inspect message size – there is one to inspect *attachment size*, which will consider each attachment separately. See Transport Rule Predicates in Exchange 2010 docs.


Shaffi Sait August 2, 2011 at 5:13 pm

Ok so if I change the global settings to send/receive 25MB does that mean all users are allowed to send/receive attachments up to that size or do I also need to specify the size for each of the users?


Bharat Suneja August 2, 2011 at 7:04 pm

Per-user settings should only be used as exceptions to org settings – they’re not set by default and you shouldn’t need to.


Cemberde September 2, 2011 at 1:53 pm

Great article!
Ok, all of the mailboxes that we migrated over from Exchange 2003 have their send/receive limit set to 4 MB. We want them to use the Exchange 2010 global settings and not have anything set individually. How do we get rid of the 4 MB limits?


Bharat Suneja September 5, 2011 at 7:35 am

Use this command to get a list of all mailboxes with MaxSendSize or MaxReceiveSize set to a non-default value:
Get-Mailbox -FIlter {MaxSendSize -ne $null -OR MaxReceiveSize -ne $null} | ft Name,MaxSendSize,MaxReceiveSize

This command sets all mailboxes with a non-default MaxSendSize or MaxReceiveSize to their default value (unlimited):
Get-Mailbox -FIlter {MaxSendSize -ne $null -OR MaxReceiveSize -ne $null} | Set-Mailbox -MaxSendSize unlimited -MaxReceiveSize unlimited


Cemberde September 7, 2011 at 7:58 am

Worked perfectly! Thanks!


solgi December 11, 2011 at 1:20 am

please help me…i cant see attach file when i forward mail with attach file in microsoft outlook but when i see mail box with web browser i can see my attach file in mail forward..what is wrong please help me immediatly


GGeisz October 20, 2011 at 2:44 pm

Awesome walk through, being an exchange novice I depend on well written documents such as this to help me.

Thanks so much


Gregory Scholz November 4, 2011 at 3:21 pm

So what really is the use for the per mailbox send/recieve limits? It seems that it would only be valuable if you have a high limit for your org and want to set some/most people to less than that. But that seems like a lot of effort and then should be done manually everytime you create a new mailbox.

Our situation is that we want just a particular user or group of users to be able to recieve large emails from the Internet. Imagine if you have an art department with valide need to recieve large work via email. But the only way to do this is with the Org config and Hub-transport recieve connector. But then that opens it up for everyone, correct?


Russel November 17, 2011 at 12:54 am

What an excellent article. You should do this sort of thing for a living.


Memi December 6, 2011 at 10:30 pm

what is the right cmdlet, that i want to list a data that contain : all users,filter by department and mailbox database then export it to csv .


Jeff December 14, 2011 at 12:17 pm

I did all of this… I have 2 companies that want to send 15 MB files to eachother…So I set the transportconfig to 25MB, I set send/receive to 25MB, and still they get the same error with the 10MB limit. Makes no sense at all!! What else could be needed? I even went to a few ppl and set just their send receive to 25MB, which is pointless because it’s the global setting…or I thought as described above. What am I missing? I checked everything in EMS and dont see a single field that doesn’t show 25MB for attachments.

:-( What am I missing?


Jeff December 14, 2011 at 1:29 pm

I get the feeling I need to restart the Microsoft Exchange Transport Services too. that makes sense to me….will try that off production hours and update.


Bharat Suneja December 15, 2011 at 1:45 am

Are the send/receive connectors between the two companies authenticated? Else limits for anonymous (i.e. lowest limits along the path – global/Org limit or Send/Receive connector limits) apply.


Rob September 4, 2012 at 6:18 pm

Assuming you only have one Hub Transport Server, your issue may be related to Attachment Size Limits. This was the missing link in my EX2010 SP1 server. Try the following cmd in Exchange Console:

Set-TransportConfig -ExternalDsnMaxMessageAttachSize 25MB -InternalDsnMaxMessageAttachSize 25MB

To verify settings have taken effect (and get some other detailed info regarding the connector), type:


In general, any “set-” cmd can also be used as a “get-” command to view the information before you make modifications.

Hope this is helpful!


Varun December 20, 2011 at 7:51 am

Thank you,
Good one.


Rory January 6, 2012 at 6:15 am

Fantastic job, thanks!!


Sunny January 26, 2012 at 11:54 am

Great article!! Helped to clarify with attachments which I was struggling with. Thanks!


Anish February 1, 2012 at 6:08 pm


For my client (ex2010)we have an internal limit of 100mb limit and any incoming or outgoing outside the organisation we have 20mb limit. we would like to set one particular mailbox to send and receive 50mb from outside the organisation. if i do it from the hub transport that will change it globaly which i don’t want.


Bharat Suneja February 2, 2012 at 12:31 pm

@Anish: As stated in the post, Internet mail is sent/received to/from anonymous recipients. For the individual exception to work, a message size must be within the allowed sizes of both sender and recipient. You can’t configure an exception for anonymous.


webfoo February 5, 2012 at 3:05 pm

Awesome saved my bacon before a migration. Thanks


JanSch February 7, 2012 at 8:09 am

Thanks. This solved my problem.


Kurt March 6, 2012 at 4:31 am

Thank you very much, fixed some issue over here :)))


sunny April 3, 2012 at 2:50 pm

for me it worked only after i restarted the Microsoft Exchange Transport Services .thx


Bharat Suneja April 24, 2012 at 12:45 am

There may be some latency due to caching and Active Directory replication. Restarting service generally helps pick up the latest config changes use when you want the changes to kick in immediately.


Aigars April 4, 2012 at 7:55 am

when I launch these ones:
To track messages that failed because of recipient’s MaxReceiveSize:

Get-MessageTrackingLog -EventID FAIL | where {$_.RecipientStatus -like “*RecipSizeLimit*”}

To track messages that failed because of the sender’s MaxSendSize:

Get-MessageTrackingLog -EventID FAIL | where {$_.RecipientStatus -like “*SendSizeLimit*”}

I get

WARNING: There are more results available than are currently displayed. To view them, increase the value of the
ResultSize parameter.

what parameters do I need to run it properly?


Bharat Suneja April 24, 2012 at 12:42 am

By default PowerShell returns 1000 results. You can specify a lower/higher number or unlimited.

See ResultSize parameter description in Get-MessageTrackingLog cmdlet help:


Shiraz April 22, 2012 at 1:32 am

Hi Andrey,
Loved your strong comment :) Seems someone stole words of my mouth. However, did you get a +ve response on the logic by some MS technical guy?


cshakeer May 25, 2012 at 12:47 am

Ok so if I change the global settings to send/receive 25MB does that mean all users are allowed to send/receive attachments up to that size..rght ???? if i need it only for few users how do I configure the same ?


Bala June 5, 2012 at 4:15 pm

thanks for the detailed info, fantastic job.


Bharat Suneja August 13, 2012 at 11:20 pm

Thanks for the feedback!


Sameer Desai September 13, 2012 at 5:38 am

Hi Bharat,

I have 2 ex2007 sp2 hub serves and have 15 mb send and rec limits sent on global settings and on connectors. I changed its value to 25 mb and restarted transport services .Still user is not able to send email with attachment of more than 14 mb. May i missing any configs ?


James Lockwood September 17, 2012 at 7:51 am

thanks very much. worked perfectly. :0) xx


Robert Krpoun November 2, 2012 at 10:47 am

Very useful… thank you!


Carmine January 18, 2013 at 2:07 am

Please help me .. still doesn’t work !!


Lukas March 1, 2013 at 6:52 am

Hi, thanks for the great article, but i think you should also change the value “Transport Dumpster” in the global Transport Settings. Otherwise the message Limit would be 18MB (Default value). The value should be 1.5 tims of the max size Limit (so 60MB in your case).
Greetings, Lukas


Hari March 19, 2013 at 10:53 pm

I am also facing this same problem in exchange 2010 while sending more than 10 MB emails.i have changed mail size limit upto 20 mb in both send connector and global settings and also did restart the server.But problem is not solved yet. Actually i have two accepted domains in the server. ex , & is true .but in send connector is showing. domain is sending failure delivery message while sending more than 10 MB i need to change to in send connector ?or is this an another issue ??Looking forward to hear you soon


Ayman April 14, 2013 at 8:10 am

many thanks


Frank P April 17, 2013 at 11:28 pm

Hi guys,
I’m pulling my hair off with this. I had a request to augment from 10Mb to 40Mb the allowance and I’ve done everything I know:

– Set the Transport Settings to 40Mb
– Set every single Receive Connector to 40Mb
– I don’t have individual mailbox maxsend /maxreceive limits
– Followed Rob Sept2012 advice to set ExternalDsnMaxMessageAttachSize and InternalDsnMaxMessageAttachSize to 40Mb
– Verified Email hosted security size is set to 50Mb
– Did all those settings 24 hours ago so restart services is out of the question

So, Why my messages both internally and externally are still rejected????? I’m sending a 15Mb message which it 30% is less than 20Mb. OMG!!! I’m sure that I’m missing something stupid.

BTW: This thread has been very informative hope you guys can help me.


Bharat Suneja April 18, 2013 at 2:01 pm

What does the DSN/NDR say?


Frank P April 18, 2013 at 7:15 pm

Hi Bharat,
Thanks for your reply. This is an NDR from internally:

This message couldn’t be delivered
554-5.3.4 message exceeds fixed system limits 554 5.3.4
STOREDRV.Deliver.Exception.MessageTooBigException.MapiExceptionMessageTooBig; Failed to process message due to a permanent exception with Message Cannot complete delivery-time processing.

And this is from an external sender:

Delivery has failed to these recipients or groups:
[email protected]
The recipient won’t be able to receive this message because it’s too large.

The maximum message size that’s allowed is 15 MB. This message is 17 MB.

Diagnostic information for administrators:

Generating server:
[email protected]
#550 5.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient ##

Original message headers:

Received: from [sender] by
[sender] with mapi id
14.01.0355.002; Thu, 18 Apr 2013 13:56:35 +0800
Content-Type: application/ms-tnef; name=”winmail.dat”
Content-Transfer-Encoding: binary

To add more frustration to my picture. I restarted Transport Service and Information Store Service and nothing. Also I, verified ADSI edit and the message size are OK.



Hartmann November 19, 2014 at 3:10 am

Dear Frank P,

What do you mean by “Verified Email hosted security size is set to …”

And i’m experiencing same issue as you!

If either you’ve resolved your incident, please share with me the solution.

Thanks for your time to read and reply.


Michael Beims October 10, 2013 at 10:21 am

Thanks! This was extremely helpful, and I love the graphics and powershell commands too.

I had to adjust the Send limit before the large messages would be “Received”. Just silly, but it works now.

Thanks to All!


Josh Ferguson October 11, 2013 at 8:50 am

Worked great, although I had to restart Outlook on the machine that was expecting the large attachment before it would pick up the new settings from the Exch server.



Rino November 6, 2013 at 1:04 am

Hi, I would like to add that there’s around 10MB overhead being added for external emails so if you’re expecting to receive a 30MB email (body + attachment), your hubs must be configured to receive 39MB at least.


Thomas April 24, 2014 at 7:22 am

I have a DB that has the mailbox size limits set at 2GB.

I need to reduce that to 200MB. There are a few users that have mailbox sizes of 400MB or above.

My question is what will happen to the mailboxes that are above 200MB when I set the DB limit to 200MB? I assume nothing will get deleted , but that the users will start to get ‘Mailbox Full’ messages.

Is that right?



Paris Wells May 26, 2015 at 4:54 pm
Felipe Almeida June 30, 2015 at 1:36 pm

Well, if I understood right, if I change the size limits for an specific user(mailbox), it won’t override the limits applied in my Organization if the email is to be sent to the internet. It only overrides internally, correct? But I tried to increase the size in my Organization and even with that it didn’t work. I have a Edge server used to send/receive email to/from internet (outside). But the error message that I get is from my internal server, not the edge server.

I don’t know where to check or change the size limits anymore.

Now, even if I attach a file in Outlook and it is bigger than 10MB, Outlook shows an error message saying that I do not have rigths to send larger files.

I am lost where to look and configure the right way.

Thank you.


Bharat Suneja July 1, 2015 at 2:30 pm

See the tracking logs (commands in the post) on internal hub or the Edge to see which server generated the error. What are the limits?


Leave a Comment

{ 16 trackbacks }

Previous post:

Next post: