asked on Message Size Exceeds Size Limit Even Though Limit is Higher
Our client often gets complaint's from their customers not being able to send attachments through to them because they continuously get rejected for being too large.
They're using an on-prem 2010 Exchange server.
The initial message size limit send/receive was set to 30MB.
Their hosted anti-spam solution, Trend micro, has a limit set for 50MB.
I changed the on-prem 2010 Exchange server send/receive to a limit of 50MB for troubleshooting purposes.
We still get bounce backs when sending anything typically over the size limit of 15MB. The message comes back indicating it exceeds the limit of 20MB. After checking all the settings (that I know of), I don't know where the size limit of 20MB is being set. I know that messages grow in size beyond the initial attachment limit, but not to this degree.
Is there anything specifically I've missed in checking?
Thank you!
They're using an on-prem 2010 Exchange server.
The initial message size limit send/receive was set to 30MB.
Their hosted anti-spam solution, Trend micro, has a limit set for 50MB.
I changed the on-prem 2010 Exchange server send/receive to a limit of 50MB for troubleshooting purposes.
We still get bounce backs when sending anything typically over the size limit of 15MB. The message comes back indicating it exceeds the limit of 20MB. After checking all the settings (that I know of), I don't know where the size limit of 20MB is being set. I know that messages grow in size beyond the initial attachment limit, but not to this degree.
Is there anything specifically I've missed in checking?
Thank you!
Chat / IMExchangeEmail ServersAntiSpamSBS
Last Comment
timgreen7077
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
If you want to modify all ReceiveConnectors, do this:
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 50MB
Set-ReceiveConnector '<Receive Connector Name>' -MaxMessageSize 50MB
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks, Jason! I've made these modifications and am currently testing.
Atachements are usually UU or Mime encoded. This allows 8 bit data to be transmitted over systems that only handle 7 bit data, at at the expense of bloating files sizes. Also, sometimes base2 kbytes are used, sometimes base10 Kbytes. Thus, 50MB may be either 50000000 bytes or 52428800. Also, there is some space used by the message body itself, as well as added on headers.
Add all these factors, and it is common for an 8Mb attachment to be bounced by a server configured with a limit at 10Mb.
Add all these factors, and it is common for an 8Mb attachment to be bounced by a server configured with a limit at 10Mb.
Enough information provided for user to make needed changes.
Thanks for these! The transport config is reflecting what was changed to 50MB. The Receive and Send Connectors are showing 20MB so this is where the issue relies. I know how to modify the send connector but cannot find the settings in the EMC to modify the receive connector.
Thanks!