On Wed, 26 Dec 2007, Derek Xu wrote:
The software was compiled and installed on a test machine running
Solaris 10. The PASSWD=PAM. The test machine is a ldap client.
Wait a second. You set PASSWDTYPE=pam? You need to set PASSWDTYPE=pmb on
Solaris because Solaris' implementation of PAM has a defect that does not
pass the userid and password from the appdata_ptr. I'm surprised that
you're getting any authentication at all because usually you get a SEGV
via a null pointer if you use the standard PAM module on Solaris.
All of these
Dec 26 10:10:14 poisson imapd[28495]: [ID 323218 mail.debug] tid= 1: unlocking
sessionLock
messages must be from LDAP in PAM or something, because they are not from
imapd.
So, ignoring all these bogus "tid=" messages, we find:
Dec 26 10:13:21 testmachine imapd[28515]: [ID 234311 mail.info] Login
user=tester host=testmachine [192.168.1.23]
Dec 26 10:13:21 testmachine imapd[28515]: [ID 960700 mail.info] Logout
user=tester host=testmachine [192.168.1.23]
as the only messages which actually came from UW imapd.
You report this in the second, "normal" case. So, it looks from this as
if in your first, "failed", case that UW imapd was never started; or at
least it did not login as the user since there is no Login or
Authenticated message reported.
Also, you should have seen another message looking like:
Dec 26 10:13:21 testmachine imapd[28515]: [ID ?????? mail.debug] imap
service init from 192.168.1.23
but maybe you don't have your mail logs set up to record debug messages.
If you don't have debug level set for your mail syslog, that's the next
thing that you ought to change since the "service init" message will
confirm if imapd ever starts.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
