On Fri, 4 Jul 2003, The Little Prince wrote: > On Sat, 5 Jul 2003, Emerson Maat wrote: > > > Hi to all, > > > > I just installed qpopper4.0.5 on my linux box. I can connect on port 110 on > > my machine using telnet locally. > > > > When I do telnet on port 110 on my machine using different machine with > > different IP, I got a message saying 'Connecting To mydomain.com...Could not > > open a connection to host on port 110 : Connect failed'. > > 1. Make sure mydomain.com resolves to an IP address that is bound to the > network card on the server that has qpopper on it. > 2. Make sure there's no firewall on the client machine restricting TCP > connections outgoing to port 110 > 3. Make sure there's no firewall on the server machine restricting TCP > connections incoming to port 110 > 4. Make sure there's no firewall/router in between the stated machines > restricting said port > > --Tony >
The suggestions above are excellent; however I believe the problem is more basic. The documentation specifically states that you'll need to add a popper: line to your /etc/hosts.allow. Read the PDF documentation for full details, but in a nutshell you have a TCP wrapper starting the deamon from xinetd. The wrapper will disallow connections from IPs it hasn't been instructed to accept. For instance, my hosts.allow has a line which reads like popper: 172.16.20.2,10.0.0.3,10.0.0.4 where the first IP is that of my mail proxy and the next two are IPs of workstations on my LAN. Actually, I just noticed this question is also covered in the FAQ. Read this for further info. http://www.qpopper.com/qpopper/faq.html#xinetd HTH. -- -chort AKA Brian Keefer The thoughts I express are generally piped from /dev/random, needless to say they do not represent my fine employer: CipherTrust, Inc - www.ciphertrust.com
