In message <[email protected]>,
Viktor Dukhovni <[email protected]> wrote:
>Spawn launches a new {policy} process for each new {SMTP} connection.
Thank you! I most certainly did not grasp that until just this moment.
>A policy server connection never outlives the smtpd(8) process that
>is its client.
I wish that both of the above statements and/or the general concept
of the one-to-one correlation between running policy daemon instances
and incoming SMTP sessions had been noted at the very top of the
SMTPD_POLICY_README document.
That would have prevented a lot of confusion on my part.
>The number of requests depends on max_use, the
>number of requests per mail transaction (per RCPT requests for
>example) and the number transactions per connection. There is no
>default absolute ceiling. The 100 is just an approximation.
>
>> My question is just this: After Postfix has sent 100 requests to a
>> given running instance of a policy server, and after it has successfully
>> received back 100 properly formatted replies from the given policy
>> server instance, then what happens?
>
>The answer is obvious. If there is an explicit request limit set,
>then the client disconnects, and the policy service sees EOF.
I think that you just utterly negated what Wietse just got done telling
me, i.e. that $max_use and the number of individual requests sent to a
given policy server are not at all related to one another.
Did I misconstrue him, or have I instead misconstrued you?
Is $max_use a limit that applies to the count of individual policy
server *requests* or not?
