On Wed, 2005-07-27 at 21:07 -0400, neidorff wrote: > On 7/27/05, Paul Howarth <paul@xxxxxxxxxxxx> wrote: > > neidorff wrote: > > >>>I'm sorry to give a flaky answer, but whatever pop server is installed > > >>>with qmailrocks. Courier does imap in this setup, I think it also > > >>>does pop. I did a manual login to the pop server > > >>>(#telnet localhost 110) > > >>>and was able to successfully log into my account and list my mail. I > > >>>assume that means that the pop server is working properly? > > >> > > >>It's at least working for localhost. It might not be listening on other > > >>interfaces. > > >> > > >>What's the output of: > > >># netstat -lpn | grep 110 > > > > > > > > > tcp 0 0 0.0.0.0:110 0.0.0.0:* > > > LISTEN 10652/tcpserver > > > > > > This tcpserver is the one that came with qmail (the ucspi-tcp-0.88 > > > package). Its the only one on the system. > > > > The netstat output indicates that it's listening on all interfaces, not > > just localhost, so it should be usable from anywhere as long as you > > don't have a /etc/hosts.deny entry or firewall rule that is blocking > > access from anywhere else. > > > > Is your kmail configured to use the pop server on localhost? > > > > Yes, kmail is configured to use the pop server on localhost. I > thought about the firewall rule and turned it off, but got the same > error. The file /etc/hosts.deny is empty (just a few lines of > comments). I've no idea why kmail can't do what you can do yourself with telnet, i.e. log in and look at your mail. What error message do you get? Paul. -- Paul Howarth <paul@xxxxxxxxxxxx>
