I tried both "pam" and "pmb". Same problem. It appears I can get LDAP authentication even if I set PASSWDTYPE to pam.
There is a service init message in both failed and succeeded cases. The following are logged messages after "tid=" entries are filtered. Case 1 (failed) Dec 26 14:12:21 testmachine imapd[1892]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:12:21 testmachine imapd[1892]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:12:21 testmachine imapd[1893]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:12:21 testmachine imapd[1893]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:12:21 testmachine imapd[1892]: [ID 960700 mail.info] Killed (lost mail box lock) user=tester host=testmachine [192.168.1.23] Dec 26 14:12:22 testmachine imapd[1893]: [ID 960700 mail.info] Unexpected client disconnect, while reading line user=tester host=testmachine [192.168.1.23] Dec 26 14:13:04 testmachine imapd[1896]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:13:04 testmachine imapd[1896]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:13:04 testmachine imapd[1896]: [ID 960700 mail.info] Logout user=teste r host=testmachine [192.168.1.23] Dec 26 14:13:04 testmachine imapd[1896]: [ID 293258 mail.warning] libsldap: Stat us: 81 Mesg: LDAP ERROR (81): Error occurred during receiving results. This may be due to a stalled connection. Case 2 (Succeeded): Dec 26 14:16:56 testmachine imapd[1928]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:16:56 testmachine imapd[1928]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:16:56 testmachine imapd[1929]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:16:56 testmachine imapd[1929]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:16:56 testmachine imapd[1928]: [ID 960700 mail.info] Killed (lost mail box lock) user=tester host=testmachine [192.168.1.23] Dec 26 14:16:57 testmachine imapd[1929]: [ID 960700 mail.info] Unexpected client disconnect, while reading line user=tester host=testmachine [192.168.1.23] Dec 26 14:17:39 testmachine imapd[1932]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:17:39 testmachine imapd[1932]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:17:39 testmachine imapd[1932]: [ID 960700 mail.info] Logout user=teste r host=testmachine [192.168.1.23] Dec 26 14:17:39 testmachine imapd[1932]: [ID 293258 mail.warning] libsldap: Stat us: 81 Mesg: LDAP ERROR (81): Error occurred during receiving results. This may be due to a stalled connection. Dec 26 14:17:39 testmachine imapd[1938]: [ID 806292 mail.debug] imap service ini t from 192.168.1.23 Dec 26 14:17:39 testmachine imapd[1938]: [ID 234311 mail.info] Login user=tester host=testmachine [192.168.1.23] Dec 26 14:17:39 testmachine imapd[1938]: [ID 960700 mail.info] Logout user=teste r host=testmachine [192.168.1.23] I noticed there are one more service init message in the succeeded case. Does that cause the "connection dropped" error message? Derek On Dec 26, 2007 12:23 PM, Mark Crispin <[EMAIL PROTECTED]> wrote: > 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
