Hi Dan
Sorry, That wasn't it either. I checked all permissions on all references to qmail-pop3d and nada. All were good. Still getting the same error.
Thanks
JJ
Main Topics
Browse All TopicsHi
I have been running qmail for several years. Recently, I had to bring up a hot backup server after a mail server crashed. The admin I put on this did NOT do a full job of installing qmail and I have had nothing but headaches re-tracing her steps. Anyway, I have the basic install of qmail up and running (it is sending and receiving emails). The trouble comes in with Qmail-pop3d. It is failing to authenticate from remote connections using user accounts and passwords I KNOW exist. Any help or suggestions would be appreciated.
Thanks
JJ
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hmmm.... you're going to have to do some investigation then... have you looked at the log files for the pop3 daemon?
Anyway, to help you dig through this, let's look at the processing path...
The REAL process that listens on port 110 (for POP access) is tcpserver (part of the ucspi package).
tcpserver gets its "instructions" for what to do upon a request at port 110 from the file:
/var/qmail/supervise/qmail
(In reality, this file actually RAN the tcpserver daemon, configuring it to listen on port 110, and describing what to do when something connects there).
In your case, you have the following options defined:
-v (verbose output for logging)
-R (do NOT attempt to get remote host IP information)
-H (do NOT do a reverse DNS name lookup on the remote host)
-l 0 (do NOT lookup yourself in DNS -- use this name (0) instead)
hostname 0
port 110
program to run = /var/qmail/bin/qmail-popup
So... I think it's safe to assume that tcpserver is working properly, or else you would be getting a server error other than "login failed"...
So next, we should look at qmail-popup: This program reads a POP3 username & password from STDIN (which was connected to the network port by tcpserver). The options are an FQDN (which means it should be more than JUST the domain name -- eg: mail.mydomain.com instead of just mydomain.com), and another sub-program. In your case, the subprogram is "/bin/checkpassword /var/qmail/bin/qmail-pop3d
So far, everything has been run as root -- so you shouldn't have any permissions errors yet...
checkpassword reads the username and password as provided by qmail-popup (surprisingly, from FD3 -- which contains the username0password0timestam
In so far as you already suspect the checkpassword program is failing, look here for a full description of how the program works:
http://cr.yp.to/checkpwd/i
It is important to note that checkpassword is used on systems where mail accounts are unix accounts! And if you're checking user passwords with Samba or something else, you may well have a problem.
You can also run into problems with PAM and checkpassword... but that's another "ball of wax"
Assuming checkpassword is successful, you'll finally run /var/qmail/bin/qmail-pop3d
For pure testing purposes, you may want to change the qmail-pop3d entry to something that writes an entry into a log file -- that way you can see if checkpassword is working (running the program), or if the called program (qmail-pop3d) is the culprit...
That's about all I have time to write just now... let me know the results of the testing I suggested above...
Dan
IT4SOHO
Business Accounts
Answer for Membership
by: it4sohoPosted on 2009-06-03 at 07:50:27ID: 24537187
Your issue appears to be a common one when people install QMail "from scratch" -- the permissions are off.
AS THE QUTHENTICATED USER
But I don't think it is the checkpassword program that is what is wrong... when /bin/checkpassword is SUCCESSFUL, it is supposed to run /var/qmail/bin/qmail-pop3d
My guess is that the permissions on qmail-pop3d are not set properly.... the MOST COMMON error I've seen is a lack of EXECUTE permission for either the qmail-pop3d folder or a parent, although it is also not uncommon to find qmail-pop3d/run also not having execute permissions allowed.
Remember though, these programs are run with the userid of the user being authenticated -- so there needs to be execute permissions (on folders and the run script) for ALL.
I hope this helps!
Dan
IT4SOHO