The LDAP search filters generated by evolution to search for addresses in the
directory are "highly ineffective" at finding people.
Here is an example of looking for a person named Kelly Smith (cn: Kelly E Smith).
# from our logs
# lets find everyone named exactly kelly smith.*, of course the person is named
Kelly E Smith, but I don't know his middle initial
# in this case the user is not found, and I become so frustrated that I do the
search using the command line ldap tool
May 11 08:51:37 peregrine slapd[15549]: conn=298480 op=41 SRCH base="o=CSUN"
scope=2 deref=0 filter="(&(objectClass=person)(|(sn=kelly smith*)(|(cn=kelly
smith*)(sn=kelly smith*))(mail=kelly smith*)(displayName=kelly smith*)))"
# here is an example of thunderbird doing a similar search for a user named
Caleb Fahey (cn: Caleb N Fahey)
# in this case the user is found on the first try, evolution would not have
found this user unless I had known his middle initial.
May 11 09:19:02 peregrine slapd[15549]: conn=300736 op=1 SRCH base="o=csun"
scope=2 deref=0 filter="(|(cn=caleb*fa*)(mail=caleb*fa*)(sn=caleb*fa*))"
In order to interoperate with organizations which store middle initials in the
cn, it is suggested that the "any" component of the substring filter (as
documented in rfc2251) be set to the last token in either the search field or
the autocomplete feild.
http://bugzilla.gnome.org/show_bug.cgi?id=304029: http://bugzilla.gnome.org/show_bug.cgi?id=304029
thanks for the bug. I've forwarded it to the evolution hackers, you can follow
it here: http://
I'll update this bugzilla according to the upstream reactions.