Author: Zahir Hussain Shah | MVP Exchange Server
Recently I been asked a question about Exchange in-bound email delivery message size limit:
Why after increasing the Exchange Server Default Receive Connector Maximum Message Size Limit, still users are receiving error message (NDR) for message exceeding the allowed 10 MB limit?
So I thought to make this painful exercise more simpler for people, who wants to increase the attachment size for in-bound or out-bound e-mail message.
| 1. In the first step, we will find the current maximum message size limit on all types of connector for examining the current situation: |
| Global Transport Settings:
Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize All Send Connectors: Get-SendConnector | Format-List -Property Identity, MaxMessageSize All Receive Connectors Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize All Routing Group Connectors for the organizations, which got transitioned from legacy Exchange versions Get-RoutingGroupConnector | Format-List -Property Identity, MaxMessageSize |
| 2. In the Send step, we will set 50 MB as the maximum size for e-mail message and attachment for in-bound and out-bound emails. |
| Global Transport Settings:
Set-TransportConfig -MaxReceiveSize 50MB -MaxSendSize 50MB All Send Connectors: Get-SendConnector | Set-SendConnector -MaxMessageSize 50MB All Receive Connectors Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 50MB All Routing Group Connectors for the legacy Exchange organizations Get-RoutingGroupConnector | Set-RoutingGroupConnector -MaxMessageSize 50MB |
I hope with these small steps, you dont have to open and giggle in between multiple GUI tabs and screen, and whenever required you can easily go back to the old configuration by simply running the CMDLets again with the appropriate MaxMessageSize limit.
Cheers!
Azure Hybrid & Cloud Migration Blog 
Leave a comment