>> I've tried pperl unsuccessfully, and I plan to try SpeedyCGI next. >> I've never heard of qpsmtpd-server or qpsmtpd-forkserver. I'll have >> to check them out.
> FWIW, the reason I wrote pperl was because I couldn't get SpeedyCGI to > compile. If it compiles for you it will probably work as it's a > different design (the backend is C rather than pure perl).
I was able to compile SpeedyCGI with no problems, and it doesn't display the wierdness that PPerl did. Load average has gone from ~7 down to 0.2.
I'd like to get one of those running. Unfortunately, I rely on tcpserver setting up its environment variables, including RELAYCLIENT, TCPREMOTEIP, TCPREMOTEHOST, etc. and qpsmtpd-forkserver doesn't set those (causing some brokenness in my database that blocked email all night long). :( So much for plug and play, eh? ;)
What migration steps and/or patches have you (all those who have implemented one or the other) taken to set and/or make those variables available when running an optimizer? I just don't want to miss anything as I migrate things over.
-- Bryan
