Author: Jeffrey C. Ollie Date: To: exim-users Subject: [Exim] Bad LDAP Lookup?
I've been having intermittent problems with LDAP lookups it seems.
Our e-mail system consists of a number of NetWare servers running
Mercury & Pegasus Mail. All of the servers are part of the same NDS
tree. Tying the NetWare servers together are two Linux servers that
run Exim v3.22 and use LDAP to query the NDS tree to get routing
information.
This setup works just great most of the time. Other times the system
will come up with an extra address that has 50 "\333" (219 decimal or
0xDB hex) characters tacked to the front of the original local part.
This only seems to happen when there are two or more user objects with
the same common name in the NDS tree and not all of the objects have a
"mail" attribute. It doesn't happen every time though. It also does
appear to be something in Exim that causes the problem because I can't
get the the command-line ldapsearch utility to return anything but
what I would expect, even after dozens of searches.
This happens on both of my Linux servers. Both servers run Exim v3.22
and OpenLDAP 2.0.7, glibc 2.2.1, and kernel 2.4.0-test12. This
happened under previous versions of glibc.
I took a quick look at the LDAP lookup code but didn't see anything
obvious. Can anyone provide any suggestions?