|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Jorey Bump (list
joreybump.com)
Date: Wed May 02 2007 - 08:56:57 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
My server has been experiencing a noncritical issue with concurrency
limits on a few remote hosts:
warning: Connection concurrency limit exceeded: 11 from
mx.example.com[192.168.1.2] for service smtp
After reading this guide:
http://www.postfix.org/TUNING_README.html#rope
I've decided to lower this parameter from the default of 20:
default_destination_concurrency_limit = 10
Related parameters inherit the change from the default settings:
lmtp_destination_concurrency_limit = $default_destination_concurrency_limit
relay_destination_concurrency_limit = $default_destination_concurrency_limit
smtp_destination_concurrency_limit = $default_destination_concurrency_limit
virtual_destination_concurrency_limit =
$default_destination_concurrency_limit
As I said, the issue is not critical, because messages were queued and
delivered within an acceptable period of time. I'm trying to reduce the
delivery delay and be kinder to destination servers during our mass
mailings. Is this the recommended approach for dealing with this issue?
I'm hoping that by halving the destination concurrency limit, I'm not
also doubling the time it will take to process a mailing (only about six
destination hosts are affected, and most of these are within our own
organization, but not under my control).
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]