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.

-----Original Message-----
From: Michael Bowe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 12:50 PM
Subject: Re: [vchkpw] Courier IMAP & vchkpw problem

make sure you compile courier using

  --without-authdaemon --with-authvchkpw


----- Original Message -----
From: "Rob Francis" <[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
> few packages, I settled for SquirrelMail (PHP pages that we could set to
> needs). SquirrelMail requires an IMAP server for authentication and
> Courier-IMAP seems to be the fastest around and recommended by most
> Everything worked wonderfully EXCEPT for the fact that you could only
> authenticate about 3 times before getting a username/password unknown
> If I restart the Courier authentication daemon it works for another 3
> I even tried setting up a cron job to run a script as root that restarts
> Courier authentication daemon every minute.
> The Courier IMAP list was the first place I searched for help but they
> adamant that the problem is with vchkpw and that I should upgrade to
> 5.3.20. I have done this but still have the same problem.
> Any suggestions? Has anyone else had this problem?

Reply via email to