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 ]

Matts (1087)

Matts
  (email not shown publicly)

I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Thursday September 15, 2005
09:01 PM

Qpsmtpd Article

[ #26739 ]

Tell everyone you know: http://www.oreillynet.com/pub/a/sysadmin/2005/09/15/qpsmtpd.html :-)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • nice job! I had a forehead-slapping "duh" moment when you mentioned one of the best ways to implement qpsmtpd is leave your existing server running on a different port and just forward all the good mail to it.

    (BTW, 'done' means I posted it on delicious, so that's basically telling everyone I know...)

  • Would help if that was actually a link [oreillynet.com]!

    • D'oh! It was on my preview because I use the Firefox Linkification extension. For some reason I just assumed that use.perl was converting it to a link.
  • I think this can count as a recent "success story" for Perl:
    As an example of the scalability of qpsmtpd, the apache.org mail servers currently process more than 2 million emails a day on their primary MX, rejecting more than 80 percent of it as junk — all thanks to the power and flexibility of qpsmtpd.

    We were in need of those, weren't we? Recent success stories?