RE: [vchkpw] Courier IMAP vchkpw problem
uummm...isn't squirrelmail php? Did you mean recompile courier-imap minus all the authentication modules aside from vchkpw? -Chris -Original Message- From: Rick Root [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 9:27 AM Cc: [EMAIL PROTECTED] Subject: Re: [vchkpw] Courier IMAP vchkpw problem On Tuesday, May 27, 2003, at 08:33 PM, Rob Francis wrote: Any suggestions? Has anyone else had this problem? Recompile squirrelmail and make sure it ONLY uses authvchkpw... get rid of tha authdaemon and all the other crap... see the previous response in this thread. that authdaemon is nothing but trouble... I had the same problem with sqwebmail. It creates more problems than it solves for most users, if you ask me. - Rick
Re: [vchkpw] Courier IMAP vchkpw problem
make sure you compile courier using --without-authdaemon --with-authvchkpw Michael. - Original Message - From: Rob Francis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 10:33 AM Subject: [vchkpw] Courier IMAP vchkpw problem Hi, I was happily using vpopmail 5.2.1 and qmailadmin. Everything was fine. However, our clients demanded some form of webmail access, so after trying a few packages, I settled for SquirrelMail (PHP pages that we could set to our needs). SquirrelMail requires an IMAP server for authentication and Courier-IMAP seems to be the fastest around and recommended by most groups. Everything worked wonderfully EXCEPT for the fact that you could only authenticate about 3 times before getting a username/password unknown error. If I restart the Courier authentication daemon it works for another 3 times. I even tried setting up a cron job to run a script as root that restarts the Courier authentication daemon every minute. The Courier IMAP list was the first place I searched for help but they were adamant that the problem is with vchkpw and that I should upgrade to version 5.3.20. I have done this but still have the same problem. Any suggestions? Has anyone else had this problem?
RE: [vchkpw] Courier IMAP vchkpw problem
Yes, I did compile with these flags but I noticed that it still uses the authdaemon. If I am not using the authdaemon, what do I type to run the Courier IMAP daemon? I thought that starting the imapd daemon would work but it seemed to start up authdaemon. Have I missed something fundamental here? The Courier documentation tells me to type: /usr/lib/courier-imap/libexec/authlib/authdaemond start If I try /usr/lib/courier-imap/libexec/authlib/authvchlpw start I get the error AUTHFAILURE Appreciate your help. Rob -Original Message- From: Michael Bowe [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 12:50 PM To: [EMAIL PROTECTED] Subject: Re: [vchkpw] Courier IMAP vchkpw problem make sure you compile courier using --without-authdaemon --with-authvchkpw Michael. - Original Message - From: Rob Francis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 10:33 AM Subject: [vchkpw] Courier IMAP vchkpw problem Hi, I was happily using vpopmail 5.2.1 and qmailadmin. Everything was fine. However, our clients demanded some form of webmail access, so after trying a few packages, I settled for SquirrelMail (PHP pages that we could set to our needs). SquirrelMail requires an IMAP server for authentication and Courier-IMAP seems to be the fastest around and recommended by most groups. Everything worked wonderfully EXCEPT for the fact that you could only authenticate about 3 times before getting a username/password unknown error. If I restart the Courier authentication daemon it works for another 3 times. I even tried setting up a cron job to run a script as root that restarts the Courier authentication daemon every minute. The Courier IMAP list was the first place I searched for help but they were adamant that the problem is with vchkpw and that I should upgrade to version 5.3.20. I have done this but still have the same problem. Any suggestions? Has anyone else had this problem?
Re: [vchkpw] Courier IMAP vchkpw problem
Perhaps take a look at how I do it I have a guide online at http://www.pipeline.com.au/staff/mbowe/isp/webmail-server.htm#COURIER_IMAP Michael. - Original Message - From: Rob Francis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 11:52 AM Subject: RE: [vchkpw] Courier IMAP vchkpw problem Yes, I did compile with these flags but I noticed that it still uses the authdaemon. If I am not using the authdaemon, what do I type to run the Courier IMAP daemon? I thought that starting the imapd daemon would work but it seemed to start up authdaemon. Have I missed something fundamental here? The Courier documentation tells me to type: /usr/lib/courier-imap/libexec/authlib/authdaemond start If I try /usr/lib/courier-imap/libexec/authlib/authvchlpw start I get the error AUTHFAILURE Appreciate your help. Rob -Original Message- From: Michael Bowe [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 12:50 PM To: [EMAIL PROTECTED] Subject: Re: [vchkpw] Courier IMAP vchkpw problem make sure you compile courier using --without-authdaemon --with-authvchkpw Michael. - Original Message - From: Rob Francis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 10:33 AM Subject: [vchkpw] Courier IMAP vchkpw problem Hi, I was happily using vpopmail 5.2.1 and qmailadmin. Everything was fine. However, our clients demanded some form of webmail access, so after trying a few packages, I settled for SquirrelMail (PHP pages that we could set to our needs). SquirrelMail requires an IMAP server for authentication and Courier-IMAP seems to be the fastest around and recommended by most groups. Everything worked wonderfully EXCEPT for the fact that you could only authenticate about 3 times before getting a username/password unknown error. If I restart the Courier authentication daemon it works for another 3 times. I even tried setting up a cron job to run a script as root that restarts the Courier authentication daemon every minute. The Courier IMAP list was the first place I searched for help but they were adamant that the problem is with vchkpw and that I should upgrade to version 5.3.20. I have done this but still have the same problem. Any suggestions? Has anyone else had this problem?
