Open
Bug 280219
Opened 20 years ago
Updated 2 years ago
inconsistency of ldap searches between the compose window and the addressbook
Categories
(MailNews Core :: LDAP Integration, defect)
MailNews Core
LDAP Integration
Tracking
(Not tracked)
NEW
People
(Reporter: dju, Assigned: aceman)
Details
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•20 years ago
|
||
I do experience the same probleme with release 1.0.4 both on a debian and on a
Mandriva linux OS.
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
Updated•18 years ago
|
QA Contact: address-book
Updated•17 years ago
|
Product: Core → MailNews Core
Updated•17 years ago
|
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
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
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•