Re: couriercheckpassword anyone?

Everyone was too slow in their replies, I've figured out my problem for 
myself.

In my userdb database file, I had set up my virtual users' passwords 
with the field name imappw since all I wanted was imap authentication.

It turns out that couriercheckpassword ignores the imappw field and 
instead looks for the systempw field within the userdb file. Once I 
changed the password field identifier to systempw, couriercheckpassword 
was able to authenticate my virtual users without a hitch. Courier 
itself will also use systempw to authenticate imap users so no need to 
have two fields with the same password for each user.

I hope someone finds this information useful and I'm not just writing to 
myself.

Andrew



Andrew wrote:
> Does anyone have couriercheckpassword working? I'm trying to get it to 
> work but I've been only partially successful.
> 
> Here is my authmodulelist parameter from the authdaemonrc file.
> 
> authmodulelist="authcustom authcram authuserdb authpam"
> 
> Using couriercheckpassword works when authenticating a system account. I 
>  know couriercheckpassword is really being used in this case because if 
> I remove authpam from the authmodulelist above, authentication for 
> system accounts stops working.
> 
> When I try to authenticate a virtual mail user, however, 
> couriercheckpassword fails. I have my virtual users in a userdb file as 
> per the documentation on the courier IMAP web site. I know courier 
> itself is able to authenticate users in the userdb file because that's 
> where my mail user account is stored and I use it every day.
> 
> I've tried removing all authentication methods from authmodulelist 
> except authuserdb but this didn't help.
> 
> Here is the command I've been using to test couriercheckpassword.
> 
> qmail-popup domain.com couriercheckpassword id
> 
> When I enter the user ID and password of a system account, I get the 
> output of the id command. If I enter the user ID and password of a 
> virtual mail account, qmail-popup returns this error.
> 
> -ERR authorization failed
> 
> Suggestions anyone?
> 
> Andrew
> 
> 
> 
>