Hello,
> I'm just about to "marry" exim (4.68) with a ADS.
> Commandline queries
>
> ldapsearch -x -H ldaps://ads:639/
>
> work fine, but Exim fails (hangs after initial TLS/SSL handshake) with:
> ldap_default_servers = server::636
> ${lookup ldap{user=... pass=... ldaps:///...}
>
> If I remove the port 636 and use plain ldap:
> ldap_default_servers = server
> ${lookup ldap{user=... pass=... ldap:///...}
If I do not have an attribute in the ldap URI, I the following output:
binding with
user=cn=tester,ou=E-Mail,....
password=Kennwort123
Start search
ldap_result loop
LDAP entry loop
LDAP attr loop objectClass:top
LDAP attr loop objectClass:person
LDAP attr loop objectClass:organizationalPerson
LDAP attr loop objectClass:user
LDAP attr loop cn:tester
...
LDAP attr loop mail:tester@autof...
It's exactly the last attribute. W/o ldaps it's the same attribute, but
then exim isn't hanging at this place.
Just loudly thinking: Could it be caused by refarrals exim gets from the
ADS, pointing back to the ADS itself? Does anybody know anything about
ADS? Is there something to configure? (I'd like to advice the ADS
admin.)
Best regards from Dresden
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann HS12-RIPE -----------------------------------------
gnupg encrypted messages are welcome - key ID: 48D0359B ---------------
gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B -
