On Mon, 15 Oct 2001 14:47:19 -0400, Stephen Bopple wrote: >I've never used Qpopper before. I downloaded the 4.0.3-no-test tarball >and installed it on a RH7.1 box. I ran > >./configure --enable-standalone enable-specialauth > >and did a make install. After editiing /etc/services to make the >change from pop-3 to pop3 I can get popper to run in standalone mode. >However, connections are being refused, and port 110 is open. >I then added: > >popper:all > >to /etc/hosts.allow (eventhough I'm not using xinetd to launch popper) >but I still cannot get a connection to port 110.
Editing hosts.allow would only affect you if qpopper had linked to tcpwrappers. I don't think it does that. The only other thing I can think of is ipchains or netfilter. Check your system logs to see if there are any firewall violations when you try to connect. You can also run tcpdump and lsof to see what your network subsystem is doing. lsof should show the listen socket. tcpdump should show some activity when you connect. Ken mailto:[EMAIL PROTECTED] http://www.sewingwitch.com/ken/ [If answering a mailing list posting, please don't cc me your reply. I'll take my answer on the list.]
