Hi Clifton, Already tried without the --enable-specialauth - even went as far as removing source and binary between each compile so I knew the options were true in each differnet configure I tried. Tried a bunch of combinations during each including nothing but the auth-file - getting the same error each time. I'll try one or two more, then I think its time to look at imap. Any debugging tips - I'm decent with reading debugs, but I'm no programmer by a long shot.
Thanks Mike -----Original Message----- From: Clifton Royston [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 21, 2002 3:18 PM To: Mike Pacheco Cc: Subscribers of Qpopper Subject: Re: qpopper 4.0 install problems On Wed, Aug 21, 2002 at 11:28:02AM -0400, Mike Pacheco wrote: > Now I am upgrading a seperate box to take its place - this one is RH 7.3 > with sendmail 8.12.5 - using qpopper 4.0 and the same install script - the > authfile is there - permission are OK - I even opened them up to 777 on > directory and file for testing once I started having problems. But > everytime I telnet localhost 110 and do > > -- > +OK ready > user xxx > +OK Password required for xxx > pass 123xyz > -ERR [AUTH] Password supplied for "xxx" is incorrect. > -- > > The password is OK - I've checked it and changed it, plus tried different > users - it OK's the user - just not the password. FYI, you can not count on this to verify anything. Popper tries to provide the identical response for invalid user and invalid password. This is troublesome when debugging, but necessary for security because otherwise it would rapidly leak information about exactly what users are valid on your system. I.e. if you put user totallybogususernotonthissystem You will still get: +OK Password required for totallybogususernotonthissystem pass chyeah,right! -ERR [AUTH] Password supplied for "totallybogususernotonthissystem" is incorrect. I just don't want you to go down a totally wrong path troubleshooting because of this. Normally qpopper's configure step automatically detects the right way to interface to the system's native authentication routines and uses them. That is, qpopper shouldn't care about MD5 hashes in the password file vs. Blowfish vs. whatever; it relies on the OS interfaces to tell it whether the user/password combo is valid. You shouldn't *need* to specify PAM, either, in most cases. It sounds to me like it's most likely that the Linux 7.3 interfaces are failing to authenticate these users to qpopper for a reason unknown. On a hunch, you might try *removing* that "--enablespecialauth" in the configure step; if the 7.3 interfaces are cleaner and easier for qpopper to autodetect, that flag might even be messing it up. If this doesn't do it, maybe try temporarily enabling some other service and try connecting to it for one of these users (FTP, telnet) and see if you can get that to authenticate for them. -- Clifton -- Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED] "What do we need to make our world come alive? What does it take to make us sing? While we're waiting for the next one to arrive..." - Sisters of Mercy
