06-28-2015 09:36 AM
Which takes precedence "maximum concurrent connections" in listener global setting, or the one set on mail flow policy in HAT?
Solved! Go to Solution.
06-28-2015 11:29 AM
"maximum concurrent connections" in listener are cumulative number of all connections from all sender hosts.
"maximum concurrent connections from a single IP" is maxumim number of connections from one sender host at a same time.
So if you set values:
maximum concurrent connections: 40
maximum concurrent connections from a single IP: 5
8 hosts will be able to initiate 5 concurrent connections at a same time.
Or if you set values:
maximum concurrent connections: 5
maximum concurrent connections from a single IP: 40
Only 1 host will be able to establish 5 connections at a same time or 5 hosts will be able to establish 1 connection at a same time.
Hope this helps.
06-28-2015 11:29 AM
"maximum concurrent connections" in listener are cumulative number of all connections from all sender hosts.
"maximum concurrent connections from a single IP" is maxumim number of connections from one sender host at a same time.
So if you set values:
maximum concurrent connections: 40
maximum concurrent connections from a single IP: 5
8 hosts will be able to initiate 5 concurrent connections at a same time.
Or if you set values:
maximum concurrent connections: 5
maximum concurrent connections from a single IP: 40
Only 1 host will be able to establish 5 connections at a same time or 5 hosts will be able to establish 1 connection at a same time.
Hope this helps.
09-07-2017 12:33 PM - edited 09-08-2017 04:30 AM
Is there a recommended value for these settings? We are using the default of 10 for 'Max Concurrent Connections From a Single IP'. And for 'Max Concurrent Connections' we use 100 (the default is 10). We are a higher ed institution and we suspect that this may be causing deferrals from some external collaborators. What indicators are there on the ESA/SMA or in the logs if a host hits the maximum? Thanks.
09-10-2017 07:39 AM
Hello,
The 'Default' values in place are the recommended; however, if you need to tweak them to fit your company needs, that is fine as well. If you're going to modify them, I would suggest doing so in smaller increments and then monitoring the System Capacity reports, as you do not want to be overloading your ESA/s.
In the case you are throttling hosts, you'll see something similar to this in the mail_logs :
Sun Sep 10 14:34:46 2017 Info: ICID 13 Receiving Failed: Connection limit exceeded
Thanks!
-Dennis M.
09-11-2017 08:03 AM
Thanks for the response. Checking our logs, I see entries like that and they do include the originating IPs. So, perhaps our customer whose connections are being rejected are not being rejected because of rate-limiting, but something else. Their email reputation isn't an issue either, so I am not clear on the cause.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide