Nick Ellson writes:

I turned on the IMAPD daemon, and tried to have PINE login to it. and I am getting CRAM-MD5 failures.

I wanted to try debugging by using telnet to the imap2 port, using md5sum to make a hash of my plaintext password contained in my MySQL database.

CRAM-MD5 authentication does not involve just taking your password and applying an MD5 hash to it. It's a completely different process. See RFC 2195.

* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2008 Double Precision, Inc. See COPYING for distribution information.
AB LOGIN "grimm" "ea7ace30b2c355ae8a25cfd102cde693"
AB NO Login failed.

No. CRAM-MD5 authentication uses a completely different command, AUTHENTICATE CRAM-MD5, and the resulting dialog is different. See RFC 2195.

And I get in my /var/log/authlog :

Dec 21 11:50:15 goonie authdaemond: pam_unix(imap:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=grimm

This shows that you are using the PAM authentication module, even though you claim that your intentions are to use authentication against a MySQL-stored account table.

Can anyone give me a nudge to some config examples of how-to's that would help me see what is going on and getting PINE reading my test mails?

See the instructions in courier-authlib's README for configuring courier-authlib to authenticate with MySQL. Do not proceed with trying to use any IMAP client until you have verified, using courier-authlib's authtest tools, that you can succesfully validate login IDs and passwords.

Attachment: pgpCi72LjkdZ1.pgp
Description: PGP signature

------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to