Success Story

[prev] [thread] [next] [Date index for 2004/12/06]

(I'm reposting this -- but in the format suggested on the
success stories page; apologies for the spam)

URL: http://www.mailchannels/opensource/
Title: Running email through mod_perl
Contact Person: Ken Simpson <ksimpson@xxxxxxxxxxx.xxxxxxxxxxxx.xxx>
Traffic: Low (in development)
Success Story: 

 We have been using mod_perl successfully for several months now as a
 flexible email proxy -- we just wrapped Net::Server::Mail and with a
 few additional hacks and it worked. Matt Sergeant did the same thing
 with qpsmtpd and I have heard that the performance results were
 initially very promising
 (http://msgs.securepoint.com/cgi-bin/get/qmail0411/120/1/1/1.html).

 More details of our hack (patches etc.) are at
 http://www.mailchannels.com/opensource and
 http://search.cpan.org/~mock/Apache-SMTP-0.01/lib/Apache/SMTP.pm.

 IMHO, using mod_perl as a general application server is a great
 idea. For us there really was no other viable alternative. We looked
 at POE, Sendmail's milter API, Net::Server and of course qpsmtpd but
 the reliability, portability, and scalability of Apache was what
 caused us to go through the effort of making our bits work on
 mod_perl.

 To configure a mail server, it's just a matter of adding a
 VirtualHost section to the Apache configuration et voila. And as
 packages such as mod_throttle move over to Apache 2, we will gain the
 wonderment of a solid resource management tool for mail traffic. Joy!

Regards,
Ken

        -- 
        MailChannels: Assured Messaging

--
Eliminate Critical False Positives
http://www.mailchannels.com
MailChannels Corporation
Suite 1600, 1188 West Georgia St.
Vancouver, BC, Canada

Ken Simpson, CEO
+1-604-729-1741

Sent by MailChannels: http://www.mailchannels.com

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html