Exchange 2013 SMTP Throttling

Posted on 2014-08-06
Medium Priority
Last Modified: 2014-08-12
I am in the process of migrating to Exchange 2013 SP1 from 2010 SP3.  In my environment, I have several .NET applications that authenticate to Exchange as an internal Exchange user and attempt to relay large amounts (1000+) messages through one of my receive connectors.  Most of these messages are bound for internal users, but there are a few that traverse my outbound send connector.  In Exchange 2010, this setup worked flawlessly.  As soon as I redirect my applications to the new Exchange 2013 server, I start getting the behavior described below.

UG Application notifications sent to intended recipients at 8/6/2014 1:00:17 AM
AU-ABC or BAS/BCM Application notifications sent to intended recipients at 8/6/2014 1:00:18 AM
Grad Application notifications sent to intended recipients at 8/6/2014 1:00:20 AM
ERROR: email@domain.com SmtpException: Service not available, closing transmission channel. The server response was: 4.4.2 Message submission rate for this client has exceeded the configured limit…

And then the last line begins repeating for multiple email addresses.

So, my first thought was that this must be a symptom of either the anti-spam or anti-malware transport agents, as I have both of these installed in my environment.  I have disabled both agents and am still experiencing the problem.  I am now thinking that this is a result of some kind of change in the throttling behavior of the transport service.  I would like some other opinions before I start to dismantle my transport service.  I also discovered that the "Get-TransportService" cmdlet has no equivalent in 2010.  Any ideas on how to get this working?
Question by:marrj
  • 4
LVL 13

Expert Comment

ID: 40243972

Author Comment

ID: 40244052
Yes, I saw that post.  My limits far exceed the defaults in Exchange and exceed the numbers I am trying to achieve.  I did try deleting and recreating the receive connector.  No luck.  Any more advice?

Mine seems to choke after only three messages.  There are only ~150 messages that are trying to go out.  Yes, the messages are all going out at a rapid rate.  I've increased my receive connector's message rate limit to 12000 to match my organizational config limit of 12000.  Still no luck.

Author Comment

ID: 40246727
Upon further investigation, I don't believe I'm having a receive connector issue.  I enabled verbose logging for the connector in question, only to find that the message seems to relay through the frontend perfectly (this is a frontend receive connector).  What I found in the frontend send protocol log are messages saying "Inbound Proxy Internal Send Connector,08D18072EB9A2BD6,1,,HT_IP:2525,*,,"Failed to connect. Winsock error code: 10061, Win32 error code: 10061, Error Message: No connection could be made because the target machine actively refused it HT_IP:2525"

So, it looks like my receive connector is working.  The message is getting rejected at the hub or somewhere else.  Any ideas on how to get more information.  I only have one server.  It has all roles installed.

Accepted Solution

marrj earned 0 total points
ID: 40247214

I think I've figured this out.  Apparently, there is a new receive connector for proxied requests in 2013 that did not exist in 2010.  Once I figured this out, I was able to adjust the MessageRateLimit to fit my needs.  The default value is 5.  This means that any frontend receive connector that depends on the frontend service to proxy requests to internal mailboxes will pass through this internal connector as well.  In a coexistence scenario, this is over TCP 2525.  

So, my issue did turn out to be a receive connector limitation, just not a frontend connector limitation.  Messages are flowing smoothly now.

Author Closing Comment

ID: 40255157
I did the research myself.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question