Maybe a little too late, but, on the subject of apache I've tried apache 2.2 and apache 2.0
Apache 2.2 is not calling to PerlProcessConnectionHandler on connect. But it's calling on first line entered by the client. (Maybe on timeout also) I've not investigated too much on this subject. (It's not calling to PerlProcessPreConnectionHandler neither) Have tried with a minimal perl on PerlProcessConnectionHandler and it hasn't worked neither. But it started working when I changed to apache 2.0 Saludos -- Leonardo Helman Pert Consultores Argentina On Mon, Nov 20, 2006 at 01:56:59PM -0500, John Peacock wrote: > John Peacock wrote: > >Good idea, but no, I already at HEAD (674). Perhaps that code doesn't > >work correctly when running under Apache? But it does give me a place > >to start throwing warn()'s into... > > Indeed, if I include the full path to the plugins directory (i.e. *not* > relative to the Qpsmtpd directory), my plugins load under Apache. > However, I am not getting any greeting at the remote side until swaks > sends the QUIT command (30 second timeout), so there is some buffering > problem somewhere. > > To reiterate, I am running Apache 2.2, built with APR 1.2.2. I'm not > seeing anything obvious in the Changes file for APR, but I'm guessing > that something isn't working as designed. Nothing has changed on the > Apache::Qpsmtpd side for a long time, so I have to assume it is the > newer Apache/APR that is causing problems (sadly those are the system > versions with SLES-10). > > I'm going to fallback to forkserver (since that seems to work just fine) > and rely on someone else with more knowledge of Apache/APR internals to > fix Apache::Qpsmtpd... > > John
