Anyway, while on this thread it has occurred to me to ask
why put qmail in either inetd or tcpserver? Why not run
it as a daemon?
1) If it ran as its own daemon, it would require root privileges to
bind to port 25. When it is spawned by tcpserver, the amount of code
requiring
- Original Message -
From: Chris Johnson [EMAIL PROTECTED]
To: Qmail List [EMAIL PROTECTED]
Sent: Friday, August 18, 2000 11:02 PM
Subject: Re: CHANGING INETD
On Fri, Aug 18, 2000 at 08:54:54PM -0700, Greg White wrote:
qmail will work fine as a daemon, but you get some really handy
[EMAIL PROTECTED] wrote:
what consequence could happen changing inetd for ucspi-tcp?
I have a mail-server, Sendmail 8.9.3 (by the moment), web server (APACHE)
Thanks
Nothing but good consequences, tcpserver works very well. Sendmail
should work fine with it, though I have never
Dale Miracle [EMAIL PROTECTED] writes on 18 August 2000 at 17:38:45 -0400
[EMAIL PROTECTED] wrote:
what consequence could happen changing inetd for ucspi-tcp?
I have a mail-server, Sendmail 8.9.3 (by the moment), web server (APACHE)
Thanks
Nothing but good consequences,
David Dyer-Bennet wrote:
Nothing but good consequences, tcpserver works very well. Sendmail
should work fine with it, though I have never personally run sendmail
with tcpserver. Apache on the other hand I don't think will run with
tcpserver. I would keep apache in inetd. You can
--- David Dyer-Bennet [EMAIL PROTECTED] wrote:
Dale Miracle [EMAIL PROTECTED] writes on 18 August 2000 at 17:38:45 -0400
[EMAIL PROTECTED] wrote:
what consequence could happen changing inetd for ucspi-tcp?
I have a mail-server, Sendmail 8.9.3 (by the moment), web server (APACHE)
On Fri, Aug 18, 2000 at 07:46:52PM -0700, Al Sparks wrote:
Anyway, while on this thread it has occurred to me to ask why put qmail
in either inetd or tcpserver? Why not run it as a daemon? At the
moment my test box is running it in inetd because I did a quick
cookbook install. I didn't
--- Ben Beuchler [EMAIL PROTECTED] wrote:
On Fri, Aug 18, 2000 at 07:46:52PM -0700, Al Sparks wrote:
Anyway, while on this thread it has occurred to me to ask why put qmail
in either inetd or tcpserver? Why not run it as a daemon? At the
moment my test box is running it in inetd
SNIP
New to list, new to qmail (running a test box right now and still
trying to decide whether to switch frm sendmail).
Anyway, while on this thread it has occurred to me to ask why put qmail
in either inetd or tcpserver? Why not run it as a daemon? At the
moment my test box is running
On Fri, Aug 18, 2000 at 08:54:54PM -0700, Greg White wrote:
qmail will work fine as a daemon, but you get some really handy
functionality from running it under tcpserver:
1. RELAYCLIENT environment variable on a per-ip basis.
2. The ability to trivially add rbl filtering to disallow dirty
10 matches
Mail list logo
