ok, I've been lurking via nntp for a while, but haven't posted to the
list until now...
I upgraded to my forkserver install to 0.40, and everything works great.
then I started playing around with the async server on an alternate
port, and noticed something strange...
the box I have qpsmtpd running on has 5 network interfaces
eth0 - internal wired
eth1 - external uplink
eth2 - wireless
tap0 - vpn
lo - localhost
only 4 of which will accept connections on port 25 (I actively drop 25
coming from the wireless network).
with the forkserver setup, telnet to the ip for any of eth0, eth1, tap0
or lo, and I receive the welcome banner
220 xxxxxx.xxx ESMTP qpsmtpd 0.40 ready; send us your mail, but not your
spam.
with async running on another port, if I telnet to eth0, tap0 or lo I
get the welcome banner. if I telnet to eth1 (the external net) I do
not. in the logs for the working attempt, I see
5720 trying to get config for smtpgreeting
and I don't see that in the logs for the broken attempt on the external
ip. but everything else seems to be setup correctly. if I start
issuing smtp commands in the telnet connection, it accepts them and
check_earlytalker doesn't trip. it just doesn't generate the 220
greeting, so well-behaved mtas shouldn't deliver mail...
any thoughts? since it's the same config and the same process listening
on multiple network interfaces, I'm a bit stumped about why it behaves
differently on one than it does on the others......
- mark
