Re: initial_destination_concurrency and too many sessions

2016-07-29 Thread Viktor Dukhovni
On Fri, Jul 29, 2016 at 05:41:25PM -0400, Alex wrote: > 279628D68138D33026 Fri Jul 29 17:09:21 salest...@example.com > (host mailstore1.secureserver.net[72.167.238.32] refused to talk to > me: 421 p3plibsmtp01-06.prod.phx3.secureserver.net bizsmtp Connection > refused, too many sessions from

Re: initial_destination_concurrency and too many sessions

2016-07-29 Thread Wietse Venema
> I realize that by setting initial_destination_concurrency to 1 it's on > a per-domain basis, which is what I believe I need. That is not what the documentation says. First, it is a different parameter name that causes the switch in concurrency scheduling, and second, the behavior is the exact op

initial_destination_concurrency and too many sessions

2016-07-29 Thread Alex
Hi, I have a fedora23 system with postfix-3.0.4 configured as a mail relay and having some difficulty reaching some destinations due to apparent problems with too many concurrent connections. I'm trying to solve the problem where this relay receives mail from one of the corporate servers where it