"John Chronakis" <[EMAIL PROTECTED]> wrote:
>qmail.org and qmail's author clearlly suggest to use tcpserver for
>qmail-smtpd and this is enough for me.
>
>But there is not any clear suggestion for using daemon tools instead
>of a superserver like xinetd (inetd is out of the question).
>In addition, the "install" file from the qmail source destribution
>has an example for using inetd to launch qmail-smtpd and pop3d.
qmail-smtpd can be served via inetd, xinetd, or tcpserver. The INSTALL
file suggested inetd because it used to be the preferred method. The
current recommendation is tcpserver from ucspi-tcp. I don't know how
well xinetd works with qmail, though. One thing you need is the
ability to set environment variables based on the IP address of the
remote system. If xinetd can do that--it's been years since I've
touched it--then it should work well with qmail.
>On the other hand qmail-howto, and allmost every othe document about
>qmail, are suggesting using daemon tools.
ucspi-tcp, not daemontools, although daemontools is also recommended.
>Friends of mine working as administrators in medium size ISPs, are
>suggesting to use qmail-smtpd and qmail-pop3d
>with xinetd like they do.
Why do they prefer it to tcpserver?
>All these different oppinions confused me.
It's better to have a confusing array of options than to be stuck with
a single frustrating utility.
>I just want to know the best way to control qmail since I am
>expecting a high number of mail users.
>What I am concerned is a reliable, stable and efficient mail delivery.
You can't go wrong with ucspi-tcp + daemontools.
-Dave
