30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
MBOX-Line: From MRC at CAC.Washington.EDU Fri Jul 21 11:26:43 2006
|
|
To: imap-protocol@u.washington.edu
|
|
From: Mark Crispin <MRC@CAC.Washington.EDU>
|
|
Date: Fri Jun 8 12:34:37 2018
|
|
Subject: [Imap-protocol] LDAP authentication not working for IMAP
|
|
In-Reply-To: <44C11A97.1020304@gentoo.org>
|
|
References: <4BFB6FF40EDF44418F01C60A094D1E7009C80A7A@FSTDKA98>
|
|
<Pine.WNT.4.65.0607210909290.2252@Shimo-Tomobiki.panda.com>
|
|
<44C10CD8.8030602@gentoo.org>
|
|
<Pine.WNT.4.65.0607210935130.2252@Shimo-Tomobiki.panda.com>
|
|
<44C11A97.1020304@gentoo.org>
|
|
Message-ID: <Pine.WNT.4.65.0607211025500.896@Shimo-Tomobiki.panda.com>
|
|
|
|
On Fri, 21 Jul 2006, Jan Kundrt wrote:
|
|
> Well, provided the uw-imapd uses the standard glibc calls, a properly
|
|
> configured nss (/etc/nsswitch.conf) should be enough. It's a system's
|
|
> configuration, not the imapd's one. I'm not familiar with the uw-imapd
|
|
> internals, though, and we're off-topic here :).
|
|
|
|
UW imapd uses getpwnam() and getpwuid(). It also, if configured for PAM
|
|
authentication, uses PAM for password validation. It has no internal
|
|
knowledge of LDAP.
|
|
|
|
-- Mark --
|
|
|
|
http://staff.washington.edu/mrc
|
|
Science does not emerge from voting, party politics, or public debate.
|
|
Si vis pacem, para bellum.
|
|
|