You create a throttling policy that contains the MessageRateLimit parameter in a Microsoft Exchange Server 2010 environment. For example, you set the value of the MessageRateLimit parameter to 1.
Note The MessageRateLimit parameter specifies the number of email messages that can be submitted to transport every minute.
You apply the policy to a user.
The user sends email messages at a rate that is greater than the limit that is set in the MessageRateLimit parameter by using Microsoft Outlook 2010 in Cached Exchange Mode. For example, the user sends two email messages in one minute.
In this scenario, email messages that are sent after the limit is exceeded are not delivered later and are moved to the Sent Items folder unexpectedly. Additionally, the user does not receive a non-delivery report (NDR).
In the example that was mentioned earlier, the second email message is moved to the Sent Items folder. Additionally, the email message is not delivered later.
Note If the user sends email messages by using Outlook 2010 in Online Mode or by using Outlook Web App, the excess email messages are also not delivered later. However, the second email message is moved to the Outbox folder or to the Drafts folder.
This issue occurs because the Microsoft Exchange Mail Submission service on the Exchange Server 2010 Mailbox server incorrectly handles a certain value that is returned from the Hub Transport server.
To resolve this issue, install the following update rollup:
2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Set-ThrottlingPolicy cmdlet, go to the following Microsoft website: