The K2 Knowledge Centre has the following KB article detailing the changes that needs to be applied to Microsoft Exchange 2010 to Increase the maximum emails per minute limitation.
Some questions that came up relating to this article were:
- The article mentioned an error message in the error logs. The error message: "Message submission rate for this client has exceeded the configured limit". Is this only on the exchange server or does it also get logged in K2 logs?
I believe this shows up in K2 logs as it can be seen via Workspace.
- The 30 email message sent per min is that the default configuration from exchange?
The default value for a Receive connector that is configured on a Hub Transport server is unlimited. The default value for a receive connector that is configured on an Edge Transport server is 600 messages per minute.
Assuming you’re NOT using an Edge server, the -MessageRateSource is already unlimited. That means you’re hitting one of the other limits, probably the -MaxInboundConnectionPercentagePerSource (default 2%) or -MaxInboundConnectionPerSource (default of 100).
e.g. If your -MaxInboundConnection is 5000, then 2% of that would be 100 if there were no other connections in use. If there were already 100 connections in use then it would be the remaining 4900*0.02 or 98.
- I want to understand how K2 handles the 30 email message per min. If K2 exceeds that, is there a method that retries it after the min to process any additional emails until it is cleared up? Will K2 continue to queue up the emails and process it or will it just stop?
Unfortunately, K2 does not currently automatically retry or queue email messages when this error is encountered.
For some additional information on Exchange message rate limits and throttling please refer to the following Microsoft article: https://technet.microsoft.com/en-us/library/bb232205%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
