On 4/20/05, Peter J. Holzer <[EMAIL PROTECTED]> wrote: > So I think a prefork hook which is called just before the fork would be > best. Arguments should probably be $client (the socket) and $hisaddr. > > Comments?
if qpsmtpd plugin compatibility is to be maintained across process management architectures (I imagine a process pool model, like apache's) we'd want to define this hook in terms of how it fits into the flow. Calling it PREFORK would work, yes, but maybe PREGREET might be better. Forkserver behavior could then be defined as a PREGREET hook.
