On 2/26/2016 11:13 AM, Saskia van Schagen wrote: > Not quite true, one can set smtpd_policy_service_request_limit to 1 and have > a new connection for each request.
Yes, you can force a new connection for each request, which will reduce performance considerably. This should only be used if the policy service is incapable of processing multiple requests over the same connection. > But even if you don't and you keep using the same connection, Postfix is > still not giving the next request before receiving the answer of the > previous request. One smtpd process --> one policy service connection. The connection stays open as long as the smtpd process runs. A busy server may have thousands of active smtpd processes, each with its own connection to the policy service. > This is not strange, if you talk over the same pipe, > Postfix could never know to what request the answer belongs to, cause we're > talking over 1 pipeline / socket. So with this design, it's not strange that > Postfix wants an answer before sending the next request. One socket with thousands of long-running connections to it. This is a common high performance design. -- Noel Jones
