I observed a similar behavior with my openLDAP/qmail installation. I
can't remember for sure what I did, but I believe that if you index
objectClass, mail, and mailAlternateAddress, it won't have to search
each of those attributes individually to find whether they match.
On a related note, part of my problem was that the access control
lists were very complex and ACL processing really slowed things down. I
have since decided to just bind as LDAP rootdn and that makes it much
faster...
Mark.
nick wrote:
>
> Ive been playing around with qmail-ldap & openldap for a little
> while, and I just noticed this in the openldap logs. I only have
> 4 entries in the database, [EMAIL PROTECTED],
> [EMAIL PROTECTED] and so on. Now this is the output that was
> generated (and chopped up since this is an email) by sending
> only one email to [EMAIL PROTECTED]
>
> Can someone clue me in as to why the ``mail`` and
> ``mailAlternateAddress`` attributes of every other entry are
> searched after it already found the entry for
> [EMAIL PROTECTED]?
>
> And is this just normal operation for qmail-ldap, or might there
> be something wrong in the way I setup openldap?
>
> nick
