|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Noel Jones (njones
megan.vbhcs.org)
Date: Wed May 02 2007 - 11:18:26 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 11:01 AM 5/2/2007, Jorey Bump wrote:
>mouss wrote:
>>Jorey Bump wrote:
>>> -o smtpd_client_connection_count_limit=10
>>10<11.
>
>I know. I let myself get distracted by the word 'concurrency'
>instead of focusing on the basic math. My bad. :P
>
>Unfortunately, my notes don't indicate why I set that option, so
>I'll raise it to 20. I have a spampd proxy listening on port 10025,
>and I don't want to overwhelm it with the default limit of 50.
Given your master.cf entry:
>smtp inet n - n - 20 smtpd
> -o smtpd_proxy_filter=127.0.0.1:10025
> -o smtpd_client_connection_count_limit=10
The above specifies that there will be no more than 20 smtpd
processes running, and a single client can make no more than 10
connections at a time.
Specifying a smtpd_client_connection_count_limit less than the total
available (20) prevents a single client from using up all available
slots - this is good.
A per-client limit of 15 is probably a reasonable setting for low to
mid volume servers. Note that client that hit the "connection count
exceeded" error may experience significant mail delays, so keep an
eye on things.
--
Noel Jones
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]