I've been running it in production since March 27th. I'm pretty certain you wouldn't be a guinea pig. Hey, I doubt you'd be a sacrificial lamb either.
I run it on a PIII/933 with SA 3.0.1 and clamav 0.83 and then 0.85.1. It never complains of load with typical averages of just over 3000 'helo' and 1300 'Queued' each day. I've been working on a bundle update which includes a fresher SA, but I'll be moving the remaining 5 in the pool of MX's to Apache::Qpsmtpd this weekend. peter On 6/16/05 10:33 AM, "Justin Erenkrantz" <[EMAIL PROTECTED]> wrote: > On Thu, Jun 16, 2005 at 11:28:43AM -0400, Matt Sergeant wrote: >> On 15 Jun 2005, at 14:47, Justin Erenkrantz wrote: >> >>> As I've mentioned before, we (apache.org) are seeing our qpsmtpd >>> processes stuck in an infinite loop. We're using qpsmtpd-forkserver. >> >> Do you have apache-2/mod_perl 2.x on that box? Sounds like you're >> having problems with the server handling code and this would be a good >> opportunity to use Apache::Qpsmtpd - let it do all the connection >> handling. > > I was talking to Joe Schaefer and he said that the Apache::Qpsmtpd code still > had a bunch of bucket leaks and that we shouldn't use it. I have no desire > for us to be a guinea pig for untested code. -- justin >
