Exchange 2010 - Message Size Limits

Soldato
Joined
27 Feb 2003
Posts
7,272
Location
Shropshire
I need to put a 20MB attachment limit on Exchange 2010 (within SBS 2011). I've gone through the usual places but testing with a zipped 8MB attached gets this:

#< #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization> #SMTP#

Double checking settings:

Code:
[PS] C:\Windows\system32>Get-TransportConfig | fl MaxSendSize, MaxReceiveSize

MaxSendSize    : 10 MB (10,485,760 bytes)
MaxReceiveSize : 19.77 MB (20,725,760 bytes)

Code:
[PS] C:\Windows\system32>Get-ReceiveConnector | fl name,MaxMessageSize


Name           : Default
MaxMessageSize : 20 MB (20,971,520 bytes)

Name           : Windows SBS Fax Sharepoint Receive
MaxMessageSize : 10 MB (10,485,760 bytes)

Name           : Windows SBS Internet Receive
MaxMessageSize : 19.77 MB (20,725,760 bytes)

Name           : Backup Exec
MaxMessageSize : 10 MB (10,485,760 bytes)

There is a max send & receive limit on the mailbox I'm testing with of 20MB.

So where else have I missed? :confused:
 
I kicked the Exchange Transport since we changed them but haven't done a full reboot as that would need a window agreeing.
 
External, so inbound from the Internet.

The only Send Connector was 10MB but I've just bumped it to 20MB and my 8MB test still bounced back.
 
Can you check to see if there are any limits being applied on the Sonicwall? Is the block message showing in messaqge tracking on the Exchange box?
 
Last edited:
On the management console while looking around exchange 2007 i noticed that there are two different places where the message limit was set. Sorry not very helpful, but i don't remember off the top of my head where exactly those two places were.
 
Can you check to see if there are any limits being applied on the Sonicwall? Is the block message showing in messaqge tracking on the Exchange box?

It's getting to Exchange. In the Message Tracking tool I can see a "RECEIVE SMTP" line, followed by a "FAIL ROUTING" line with the same error as the bounce message:

550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization
 
There isnt some kind of Exchange side forwarding on the account set to only deliver to the forwarding account which has a message size limit? Have you tried to different mailboxes?
 
No forwards on the mailbox and I've just removed the 20MB mailbox message size limit - still bounced.

Just tested to another account (that didn't have message size limit) - 8MB still bounced.
 
Odd, the error is related to sending messages as well.. have you tried just changing/upping all send/receive connector limits as well as the transport global settings incase the value is being reported wrongly, maybe check in ADSI edit too. This link will give you the pointers for where to find the limit values in ADSI edit, would consider changing in there to the limit size (don't set to "not set").

http://forums.msexchange.org/m_1800436085/tm.htm
 
Odd, the error is related to sending messages as well.. have you tried just changing/upping all send/receive connector limits as well as the transport global settings incase the value is being reported wrongly, maybe check in ADSI edit too.

You were close NightShadow. A bit more Googling turned up a this TechNet blog post with the killer line:

NOTE: Exchange considers message submission to the store driver as a “send” operation. Therefore, if you are attempting to receive an email message on an SBS server from the internet that is greater than the MaxSendSize of the global transport configuration, delivery will fail.

Whacked Global Transport send up to 20MB and, it works. I think everytime I've tweaked send/receive sizes in the past I've done both but this time we didn't want to increase the Send limit.
 
Was about to post that Exchange sees receiving mail as a send, had me confused for a day or so. Completely illogical :)
 
Thanks for posting back with the solution, most time people just leave these unanswered so credit to you :)

That drives me up the wall when I'm trying to nail problems. Somebody either never posts back if they did or didn't solve it. Or worse, they just post "fixed" and not what worked. Grrr! :D
 
Glad you got it sorted and thanks for coming back with the solution. Looks like I might have fixed it but not known the real reason behind so it's good to know!
 
Back
Top Bottom