Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

ttul (1539)

ttul
  ksimpson at ttul dot org
http://ttul.org/~ksimpson

Journal of ttul (1539)

Saturday January 08, 2005
06:06 PM

Writing an article for Perl.com

[ #22633 ]
Well, I've started writing an article for Perl.com about Apache::SMTP. So far it's going well. I hope that the article is accepted because I would like to create a community around the new project.

List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Writing an article for Perl.com 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Apache::SMTP looks neat, but is it really worth the effort to write an entire new SMTP implementation when Qpsmtpd already exists and there's already code to plug it in to Apache2/mod_perl2?
    • qpsmtpd is a nifty package that has lots of great plugins and a strong community behind it. And with the release of Apache::Qpsmtpd it will only get better. I guess the short answer is: TIMTOWTDI. In an effort to work just like qmail, qpsmtpd made certain trade offs that aren't strictly necessary for processing email -- like passing variables around in %ENV. Our goal with Apache::SMTP is to make a blazingly streamlined SMTP proxy that is designed for maximal Apache integration and minimal legacy cruft. It
      --
      MailChannels -- Get rid of false positives
    • The other thing is that Apache::SMTP predates Apache::Qpsmtpd.

      Matt Sergeant copied us -- not the other way around.
      --
      MailChannels -- Get rid of false positives
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.