Hiya --
On Wed, Jan 03, 2007 at 09:15:03PM +0100, Kjetil Kjernsmo wrote:
> The problem I'm seeing is that the qmail package binds something to port
> 25 before qpsmtpd gets the chance, so by just installing those, it
> hasn't worked for me.
This is a known obstacle in the qpsmtpd installation under Debian, and the
reason the default behavior is not to attempt to start up by default. There's
some discussion of this in the package's README, and in the debconf dialog
("Enable qpsmtpd startup at boot time?") asked when qpsmtpd is installed.
There are quite a few MTAs in Debian, and most of them listen on port 25 by
default. Automatically reconfiguring them not to isn't really feasible.
Jumping ahead in the startup order isn't really a good strategy, because it
just makes a different piece fail instead of qpsmptd.
What I suggest you do is comment out the startup of qmail-smtpd in
/etc/init.d/qmail, in particular these lines:
# prevent denial-of-service attacks, with ulimit
ulimit -v 16384
sh -c "start-stop-daemon --start --quiet --user qmaild \
--pidfile /var/run/tcpserver_smtpd.pid --make-pidfile \
--exec /usr/bin/tcpserver -- -R -H \
-u `id -u qmaild` -g `id -g nobody` -x /etc/tcp.smtp.cdb 0 smtp \
$rblsmtpd /usr/sbin/qmail-smtpd 2>&1 \
| $logger &"
This will start qmail-send ahead of qpsmtpd, but not start qmail-smtpd at all.
If you use this approach you'll probably want to be sure qpsmtpd is instructed
to listen on all port 25s by default, instead of the loopback/external
interface arrangement some folks use. You can run 'dpkg-reconfigure qpsmtpd'
to adjust this if needed.
--
Devin \ aqua(at)devin.com, IRC:Requiem; http://www.devin.com
Carraway \ 1024D/E9ABFCD2: 13E7 199E DD1E 65F0 8905 2E43 5395 CA0D E9AB FCD2
