I'm running a nearly stock 0.28 release with the mild mods to fix the
Apache::Qpsmtpd module.  I don't think I made any changes in httpd.conf.
Here's the base server-info:

Server Version: Apache/2.0.53 (Unix) mod_perl/1.99_17 Perl/v5.8.6 DAV/2
Server Built: Feb 17 2005 21:06:05
API Version: 20020903:9
Hostname/port: localhost.:80
Timeouts: connection: 300    keep-alive: 300
MPM Name: Prefork
MPM Information: Max Daemons: 150 Threaded: no Forked: yes
Server Root: /usr/pkg
Config File: /usr/pkg/etc/httpd/httpd.conf

(from netbsd's pkgsrc, otherwise pretty stock)

I run the same plug-ins as I run on the remaining forkserver.  My setup does
use my logging plugins, otherwise the log messages end up in the Apache
error_log.  You should be able to do the same with more current releases
though I can't say that I've looked at any of the updates since Feb.

---------------------------
qpsmtpd.conf (virt web conf file)
---------------------------
User smtpd
Group users

Listen 0.0.0.0:25

LoadModule perl_module lib/httpd/mod_perl.so

<Perl>
  use lib qw( /home/smtpd/qpsmtpd/lib );
  use Apache::Qpsmtpd;
</Perl>

<VirtualHost _default_:25>
  PerlSetVar QpsmtpdDir /home/smtpd/qpsmtpd
  PerlModule Apache::Qpsmtpd
  PerlProcessConnectionHandler Apache::Qpsmtpd

  ErrorLog /var/log/httpd/qpsmtpd-error_log
  CustomLog /var/log/httpd/qpsmtpd-access_log common
</VirtualHost>

---------------------------

I don't think that I'd go out of my way to run under Apache rather than
forkserver, but if you're running Apache on the system already it's a really
simple addition.  

peter



Reply via email to