3 messages in net.sourceforge.lists.courier-users[courier-users] Courier Authenticatio...
FromSent OnAttachments
Stephen MeatheringhamDec 21, 2006 3:31 pm 
Gordon MessmerDec 21, 2006 3:57 pm 
Stephen MeatheringhamDec 21, 2006 4:49 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Courier Authentication Using PAMActions...
From:Stephen Meatheringham (s.me@adfa.edu.au)
Date:Dec 21, 2006 3:31:44 pm
List:net.sourceforge.lists.courier-users

All I am currently evaluating the Courier mail package as a replacement for our student email system. I installed a test setup using local accounts which worked fine. I then blew that away, started from scratch and am now endeavouring to get everything working authenticating to our Novell eDirectory.

My test system is running under SLES10. I am using courier-authlib (0.58) and Courier (0.53.3).

I have configured my SLES server to permit LDAP authentication. I works fine. For example, I can ssh to that box using user information stored in eDirectory.

I have local authentication working fine for Courier. For example, a test user with a local account on the server can connect to the POP3 port and read their mail.

However, I have not as yet been able to get my test LDAP user to authenticate.

I have looked at various settings in /usr/local/etc/authlib/authdaemonrc and /usr/lib/courier/etc/pop3d, but am unable to find a fix in there.

Here is an example of loggin information from /var/log/mail: Dec 22 10:09:09 mailtest pop3d: Connection, ip=[::ffff:131.236.1.12] Dec 22 10:09:17 mailtest authdaemond: received auth request, service=pop3, authtype=login Dec 22 10:09:17 mailtest authdaemond: authuserdb: trying this module Dec 22 10:09:17 mailtest authdaemond: userdb: unable to stat /usr/local/etc/authlib/userdb.dat: No such file or directory Dec 22 10:09:17 mailtest authdaemond: userdb: looking up 'testuser' Dec 22 10:09:17 mailtest authdaemond: authuserdb: REJECT - try next module Dec 22 10:09:17 mailtest authdaemond: authpwd: trying this module Dec 22 10:09:17 mailtest authdaemond: authpwd: sysusername=testuser, sysuserid=<null>, sysgroupid=100, homedir=/home/testuser, address=testuser, fullname=testuser, maildir=<null>, quota=<null>, options=<null> Dec 22 10:09:17 mailtest authdaemond: supplied password does not match encrypted password Dec 22 10:09:17 mailtest authdaemond: authpwd: REJECT - try next module Dec 22 10:09:17 mailtest authdaemond: authshadow: trying this module Dec 22 10:09:17 mailtest pop3d: LOGIN FAILED, user=testuser, ip=[::ffff:131.236.1.12] Dec 22 10:09:17 mailtest authdaemond: authshadow: REJECT - try next module Dec 22 10:09:17 mailtest authdaemond: authcustom: trying this module Dec 22 10:09:17 mailtest authdaemond: authcustom: nothing implemented in do_auth_custom() Dec 22 10:09:17 mailtest authdaemond: authcustom: REJECT - try next module Dec 22 10:09:17 mailtest authdaemond: authpipe: trying this module Dec 22 10:09:17 mailtest authdaemond: authpipe: REJECT - try next module Dec 22 10:09:17 mailtest authdaemond: FAIL, all modules rejected Dec 22 10:09:25 mailtest pop3d: Disconnected, ip=[::ffff:131.236.1.12]

It is simply complaining that the passwords are not matching under authpwd. If the user exists in the local password file then it falls through to authshadow and works.

My /etc/pam.d/pop3d file is: auth include common-auth account include common-account password include common-password session include common-session

I'm new to SUSE (coming from a long SunOs and Solaris background) so if I'm missing something obvious please let me know.

Any thoughts, suggestions or a fix would be most appreciated.