inconsistency of ldap searches between the compose window and the addressbook

NEW
Assigned to

Status

defect
15 years ago
3 years ago

People

(Reporter: dju, Assigned: aceman)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041121 Firefox/1.0
Build Identifier: version 1.0 (20041221)

When typing some letters to search for a person inside a ldap addressbook, from
the addressbook window, the ldap search filter is:

filter="(|(mail=*mat*)(cn=*mat*)(givenName=*mat*)(sn=*mat*))"

so the cn=BRONSON Mathiew,ou=people,dc=example,dc=com object is displayed in the
results. However, if i do the same from the compose window, in the To: field for
exemple, the ldap filter is set to:

filter="(|(cn=mat*)(mail=mat*)(sn=mat*))"

that's why i don't find the previous object. Why are the filter different?

Reproducible: Always



Expected Results:  
the search filters should be the same imho.

Comment 1

14 years ago
I do experience the same probleme with release 1.0.4 both on a debian and on a
Mandriva linux OS.

Comment 2

13 years ago
I stumbled upon the same problem in Thunderbird 1.5. As a temporary work-around, I've used the hidden pref ldap_2.servers.MyServer.autoComplete.filterTemplate.

For more information, see http://www.mail-archive.com/mozilla-directory@mozilla.org/msg00817.html
QA Contact: address-book
Product: Core → MailNews Core
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Component: Address Book → MailNews: LDAP Integration
Ever confirmed: true
OS: Linux → All
Product: Thunderbird → Core
QA Contact: address-book → ldap-integration
Hardware: PC → All
Assignee

Comment 3

3 years ago
Maybe it is so that the autocomplete search does not block the window for seconds until the complicated search finishes. But I'm all for exposing this pref in the Advanced properties dialog of the LDAP addressbook.
Assignee: nobody → acelists
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.