Re: [exim] LDAP connection caching problem?

Pàgina inicial
Delete this message
Reply to this message
Autor: Nigel Wade
Data:  
A: exim-users
Assumpte: Re: [exim] LDAP connection caching problem?
John Dalbec wrote:
> John Dalbec wrote:
>
>> Exim 4.50, 4.52:
>> routing seems to work OK, but the delivery process (in some cases)
>> can't seem to
>> talk to LDAP. The search should return no results. OpenLDAP 2.0.x
>> library, Novell eDirectory 8.7.3.4 server.
>>
>> exim -d -M ... yields:
>>
>> after ldap_url_parse: host=... port=636
>> re-using cached connection to LDAP server ...:636
>> Start search
>> search ended by ldap_result yielding -1
>> ldap_result failed
>> ldap_result failed: 81, Can't contact LDAP server
>> lookup deferred: ldap_result failed: 81, Can't contact LDAP server
>> condition check lookup defer
>>
>> Any thoughts?
>> TIA,
>> John
>
>
> By post-hoc reasoning I worked out that a new address rewriting rule I
> had added seemed to be tickling the problem.
>
> ^([a-z]+).([0-9]+)@((?:...)ysu\\.edu)\$ "\
>         ${lookup ldap\
>         {user=... \
>         pass=... \
>         ldaps:///...?uid?sub?(uid=${quote_ldap:$1$2})}\
>         {$1$2@$3}fail}"         Eh

>
> We plan to convert our dotted local parts to undotted local parts. This
> rule is intended to make sure the dotted addresses keep working after we
> change the local parts in LDAP. We won't necessarily be able to change
> them all at once so we have to check the directory to see whether the
> correct local part is dotted or undotted.
>
> Does anyone see a problem with this rule?
> Thanks,
> John
>


Are you sure the LDAP server is listening on the ldaps (i.e. encrypted) port
636, and that it and Exim are fully configured for the encryption handshake
(TLS, SSL or whatever is being used)?


-- 
Nigel Wade, System Administrator, Space Plasma Physics Group,
             University of Leicester, Leicester, LE1 7RH, UK
E-mail :    nmw@???
Phone :     +44 (0)116 2523548, Fax : +44 (0)116 2523555