Great! Thanks! Although this wasn't the answer, it helped me in two ways. 1) I had forgotten to put imaps in my pam.conf file. 2) Watching the authentication log proved that it was actually getting to PAM. I double checked my configuration and realized I wasn't using all the modules that a standard login was using. When I changed it to below, everything worked:
imap auth requisite pam_authtok_get.so.1 imap auth required pam_dhkeys.so.1 imap auth sufficient pam_unix_auth.so.1 imap auth required pam_smb_auth.so use_first_pass imaps auth requisite pam_authtok_get.so.1 imaps auth required pam_dhkeys.so.1 imaps auth sufficient pam_unix_auth.so.1 imaps auth required pam_smb_auth.so use_first_pass I'm not sure exactly what the authtok_get and dhkeys modules do, but I guess they are necessary. ~ Chris -- Christopher Huyler [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Jahnke Sent: Monday, March 29, 2004 2:41 AM To: Christopher Huyler; [EMAIL PROTECTED] Subject: Re: imapd with PAM authentication on Solaris 8 Hi Christopher, I do not use SMB passwords, but imap(s) with PAM on Solaris 8. All my imap related entries in the pam.conf are like this: imaps auth optional /usr/lib/security/$ISA/pam_afs.so.1 try_first_pass ignore_root setenv_password_expires debug (well, "debug" only when debugging...) You can switch on debugging of PAM with syslog.conf: auth.debug /where/ever/log/pam_debug Do not forget to touch the file prior to SIGHUPing syslogd. Cheers, -- Dirk Jahnke Deutsches Elektronen-Synchrotron DESY Hamburg IT Systems / Bldg. 2b / Room 221 D-22603 Hamburg Notkestrasse 85 / 22607 Hamburg Tel: +49-40-899.8.1760 Fax: +49-40-899.4.1760 [EMAIL PROTECTED]
