Topic Last Modified: 2007-01-05
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value for the global settings delivContLength attribute located at:
CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=OrganizationName, CN=Global Settings, CN=Message Delivery
If the Exchange Server Analyzer finds the value for the delivContLength attribute to be less than 1024 but more than 0, an error is displayed.
This error indicates that a maximum incoming message size limit is set to a value less than 1 megabyte (MB). Such a low value may prevent Exchange Server from accepting some of the messages sent to your organization. In Exchange 2000 Server and Exchange Server 2007, there is no default message size limit. In Exchange Server 2003, the default size limit for sending and receiving messages is 10,240 KB. This default size limit applies to new installations and to upgrades from Exchange 2000 Server in which no message size limit was set.
You can conserve system resources by setting message size limits that prevent users from sending and receiving large e-mail messages. This will help limit network traffic, save disk space, and improve overall network performance. For Exchange 2000 Server and Exchange Server 2003, you can use the Defaults tab in Message Delivery Properties of your Global Settings to specify message delivery restrictions for incoming and outgoing messages. To set the maximum individual message size, select Maximum (KB), and then in the text box, type a maximum size, in kilobytes (KB). If you do not want to limit the size of messages, select No limit. Senders in your organization receive an NDR if they try to send a message to a user who exceeds the specified size limit. Depending on the NDR settings that you configure in Internet Message Formats, external senders may not receive an NDR.
For Exchange Server 2007, you can use the Exchange Management Shell to set the TransportConfig MaxSendSize parameter for the Exchange organization.
We recommend that you set the maximum message size limit to no more than 10 MB. However, if you need a larger message size limit for messages that have large attachments to be sent through the Exchange organization, you may want to increase the maximum incoming message size limit to 30 MB. Increasing the message size limit over 30 MB can slow down the network performance and even cause the system to be more vulnerable to security attacks.
To set message size limits for Exchange 2000 Server and Exchange Server 2003
In Exchange System Manager, expand Global Settings, right-click Message Delivery, and then click Properties.
In the Message Delivery Properties dialog box, on the Defaults tab, select the Receiving message size limit option and type the size limit you want.
To set message size limits for Exchange Server 2007
In Exchange Management Shell, run the following command where <size> is entered as the default of "unlimited" or the size in B (Bytes), KB (Kilobytes), or MB (Megabytes) in a range of 0 to 2147483647 bytes:
Set-TransportConfig -MaxReceiveSize <size>
For example, to set the maximum message size that can be received by recipients in the Exchange Organization to 10 Megabytes you would enter:
Set-TransportConfig -MaxReceiveSize 10MB
To set the maximum message size that can be received by recipients in the Exchange Organization to the default value of unlimited you would enter:
Set-TransportConfig -MaxReceiveSize unlimited
- For more information about how to set message size limits for
Exchange 2000 Server and Exchange Server 2003, see the
Microsoft Knowledge Base article 322679, "Set Size Limits for
For more information about the TransportConfig cmdlet for Exchange Server 2007, see "Set-TransportConfig" in the Exchange Server 2007 Technical Reference (http://go.microsoft.com/fwlink/?LinkID=79237).
- For more information about Internet Message Formats, see
"Configuring SMTP Policies to Control Outbound Mail Formatting and
Automatic Responses" in the Exchange Server 2003
Administration Guide (http://go.microsoft.com/fwlink/?LinkId=47617).