I'm experiencing a curious issue with qmail-popup/pop3d.
qmail-popup is being called by tcpserver. It even works.
POP3 server: wndrgrl.goldblatt.net 208.190.130.82/27
Other interface: 10.1.1.10
The 208.190.130.82 works quickly, efficiently, as expected, but in
public. This interface is a 10 megabit NIC.
The 10.1.1.10 interface is a totally separate 100 megabit LAN that I use to
run my private services, like printer sharing, NFS, all the stuff I need
but don't want exposed to the public.
When I try to retrieve mail via POP3 on the PUBLIC interface, all goes well.
When I try to retrieve mail via POP3 on the PRIVATE interface, it works,
but where the public side takes about two seconds to complete an empty
transaction, the private one takes as much as 60 seconds to authenticate
(Eudora hangs on "Logging in to server," which is its way of saying
login/password). If Eudora doesn't get sick of waiting it EVENTUALLY
works, but slowly.
qmail-popup is invoked as follows:
/usr/local/bin/tcpserver 0 110 /var/qmail/bin/qmail-popup
wndrgrl.goldblatt.net /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
Per the documentation in various places, the FQDN is
wndrgrl.goldblatt.net. Do I need -two- instances of qmail-popup -- one for
each interface? Or does tcpserver bind to both interfaces at once?
My gut reaction is that tcpserver binds to both interfaces, based on the
fact that retrieval from the private interface does work, albeit slowly.
Pointers toward a resolution or where to start looking, including FAQs and
docs I've missed, are welcome.
Thank you.
age
