The problems I saw with Apache:Qpsmtpd were that the connections would get battered over each other. Basically, spammer connects and gets blacklisted, server drops the connection and takes a new one, new connections issues a HELO and server responds back with a 50x error message. The only way to fix this was to set the forking at a 1-1 rate, which just wasn't good obviously. Never had that problem with forkserver.
On 8/15/07 6:14 PM, "Joe Schaefer" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] (Charlie Brady) writes: > >> AFAICT, nobody has ever said what constitutes 'faster', or what >> performance testing has been done forkserver v Apache::Qpsmtpd. > > When SMTP transactions are measured in seconds, "faster" really > doesn't matter unless you're talking about how quickly you can > fail a bad connection. The big win with Apache::Qpsmtpd over > forkserver at Apache, IIRC, was in measuring the ratio of forks > to connections. With forkserver, the ratio is 1-1, whereas > with Apache::Qpsmptd it's configurable within httpd, and for > apache is on the order of 1 fork per 5000 connections. -- Ed McLain Sr. Data Center Engineer TekLinks, Inc. 205.314.6634 [EMAIL PROTECTED]
