Understanding Message Throttling
Applies to: Exchange Server 2010
This topic explains the message throttling options that are available in Microsoft Exchange Server 2010. Message throttling is a group of limits that are put on the number of messages and connections that can be processed by a computer that's running Exchange 2010 that has the Hub Transport server role or Edge Transport server role installed. These limits prevent the accidental or intentional inundation of the system resources on the transport server.
Looking for management tasks related to managing transport servers? See Managing Transport Servers.
Contents
Message Throttling Scope
Message Throttling Options on Transport Servers
Message Throttling Option on Send Connectors
Message Throttling Options on Receive Connectors
Message Throttling Scope
Message throttling involves a variety of limits on message processing rates, SMTP connection rates, and SMTP session time-out values. These limits work together to protect the Hub Transport server or Edge Transport server from being overwhelmed by accepting and delivering messages. Although a large backlog of messages and connections may be waiting to be processed, the message throttling limits enable the transport server to process the messages and connections in an orderly manner.
In addition to message throttling, with Exchange 2010 you can also put size limits on the individual components of messages, such as the number of recipients, the size of the message header, or the size of individual attachments. For more information about message size limits, see Understanding Message Size Limits.
Another Exchange 2010 feature that helps prevent the inundation of system resources of an Exchange 2010 transport server is back pressure. Back pressure is a system resource monitoring feature on Hub Transport servers and Edge Transport servers. When a monitored system resource, such has hard disk utilization or memory utilization, exceeds the specified threshold, the Exchange transport server reduces the rate it accepts new connections and messages, and concentrates on delivering existing messages. When the utilization of the monitored system resources returns to normal levels, the Exchange transport server slowly increases the rate it accepts new connections and messages back to a normal level. For more information about back pressure, see Understanding Back Pressure.
Return to top
Message Throttling Options on Transport Servers
You can set the message throttling options at the following locations:
- On the transport server
- On a Send connector
- On a Receive connector
You can set all the message throttling options that are available on Hub Transport servers or Edge Transport servers in the Exchange Management Shell. You can also set some of the same options by configuring the transport server properties in the Exchange Management Console (EMC).
The following table shows the message throttling options that are available on Hub Transport servers or Edge Transport servers.
Message throttling options
| Source | Parameter | Description |
|---|---|---|
Set-TransportServer |
MaxConcurrentMailboxDeliveries |
This parameter specifies the maximum number of delivery threads that the Hub Transport server can have open at the same time to deliver messages to mailboxes. The store driver on the Hub Transport server is responsible for delivering messages to and from Mailbox servers. This limit applies to the delivery of messages to any mailboxes in the Exchange organization. The default value of the MaxConcurrentMailboxDeliveries parameter is 20. |
Set-TransportServer |
MaxConcurrentMailboxSubmissions |
This parameter specifies the maximum number of delivery threads that the Hub Transport server can have open at the same time to accept messages from mailboxes. The store driver on the Hub Transport server is responsible for delivering messages to and from Mailbox servers. This limit applies to the acceptance of new messages from any mailboxes in the Exchange organization. The default value of the MaxConcurrentMailboxSubmissions parameter is 20. |
Set-TransportServer |
MaxConnectionRatePerMinute |
This parameter specifies the maximum rate at which new inbound connections can be opened to the Hub Transport server or the Edge Transport server. These connections are opened to any Receive connectors that exist on the server. The default value for the MaxConnectionRatePerMinute parameter is 1200 connections per minute. |
Set-TransportServer or Transport server properties |
MaxOutboundConnections |
This parameter specifies the maximum number of concurrent outbound connections that the Hub Transport server or Edge Transport server can have open at the same time. The outbound connections occur by using the Send connectors that exist on the server. The value that's specified by the MaxOutboundConnections parameter applies to all the Send connectors that exist on the transport server. The default value of the MaxOutboundConnections parameter is 1000. If you enter a value of This value can also be configured using the EMC. |
Set-TransportServer or Transport server properties |
MaxPerDomainOutboundConnections |
This parameter specifies the maximum number of connections that an Internet-facing Hub Transport server or Edge Transport server can have open to any single remote domain. The outbound connections to remote domains occur by using Send connectors that exist on the server. The default value of the MaxPerDomainOutboundConnections parameter is 20. If you enter a value of This value can also be configured using the EMC. |
Set-TransportServer |
PickupDirectoryMaxMessagesPerMinute |
This parameter specifies the rate of message processing for both the Pickup directory and Replay directory. Each directory can independently process message files at the rate that's specified by the PickupDirectoryMaxMessagesPerMinute parameter. By default, the Pickup directory can process 100 messages per minute, and the Replay directory can process 100 messages per minute at the same time. The Pickup directory and the Replay directory scan for new message files once every 5 seconds, or 12 times per minute. This 5-second polling interval isn't configurable. This means the maximum number of messages that can be processed during each polling interval is the value that you assign to the PickupDirectoryMaxMessagesPerMinute parameter divided by 12 (PickupDirectoryMaxMessagesPerMinute/12). By default, a maximum of just over eight messages can be processed during each 5-second polling interval. |
For more information, see the following topics:
- Configure Edge Transport Server Properties
- Configure Hub Transport Server Properties
- Set-TransportServer
Return to top
Message Throttling Option on Send Connectors
The following table shows the message throttling option that's available on Send connectors that are configured in your organization or an Edge Transport server. You must use the Shell to configure this option.
Message throttling option that's available on Send connectors
| Source | Parameter | Description |
|---|---|---|
Set-SendConnector |
ConnectionInactivityTimeOut |
This parameter specifies the maximum time that an open SMTP connection with a destination messaging server can remain idle before the connection is closed. The default value is 10 minutes. |
For more information, see Set-SendConnector.
Return to top
Message Throttling Options on Receive Connectors
The following table shows the message throttling options that are available on Receive connectors that are configured on a Hub Transport server or an Edge Transport server. You must use the Shell to configure these options.
Message throttling options that are available on Receive connectors
| Source | Parameter | Description |
|---|---|---|
Set-ReceiveConnector |
ConnectionInactivityTimeOut |
This parameter specifies the maximum time that an open SMTP connection with a source messaging server can remain idle before the connection is closed. The default value for a Receive connector that's configured on a Hub Transport server is 5 minutes. The default value for a Receive connector that's configured on an Edge Transport server is 1 minute. |
Set-ReceiveConnector |
ConnectionTimeOut |
This parameter specifies the maximum time that an SMTP connection with a source messaging server can remain open, even if the source messaging server is transmitting data. The default value for a Receive connector that's configured on a Hub Transport server is 10 minutes The default value for a Receive connector that's configured on an Edge Transport server is 5 minutes. The value specified by the ConnectionTimeout parameter must be larger than the value specified by the ConnectionInactivityTimeout parameter. |
Set-ReceiveConnector |
MaxInboundConnection |
This parameter specifies the maximum number of inbound SMTP connections that this Receive connector allows at the same time. The default value is 5000. |
Set-ReceiveConnector |
MaxInboundConnectionPercentagePerSource |
This parameter specifies the maximum number of SMTP connections that a Receive connector allows at the same time from a single source messaging server. The value is expressed as the percentage of available remaining connections on a Receive connector. The maximum number of connections that are permitted by the Receive connector is defined by the MaxInboundConnection parameter. The default value of the MaxInboundConnectionPercentagePerSource parameter is 2 percent. |
Set-ReceiveConnector |
MaxInboundConnectionPerSource |
This parameter specifies the maximum number of SMTP connections that a Receive connector allows at the same time from a single source messaging server. The default value is 100. |
Set-ReceiveConnector |
MaxProtocolErrors |
This parameter specifies the maximum number of SMTP protocol errors that a Receive connector allows before the Receive connector closes the connection with the source messaging server. The default value is 5. |
Set-ReceiveConnector |
TarpitInterval |
This parameter specifies the delay that's used in tarpitting. Tarpitting is the practice of artificially delaying SMTP responses for specific SMTP communication patterns that indicate a directory harvest attack or other unwelcome messages. A directory harvest attack is an attempt to collect valid e-mail addresses from a particular organization to use as a target for unsolicited commercial e-mail. The delay that's specified by the TarpitInterval parameter only applies to anonymous connections. The default value of the TarpitInterval parameter is 5 seconds. For more information, see Understanding Recipient Filtering. |
For more information, see Set-ReceiveConnector.
Return to top