Closed Bug 271490 Opened 20 years ago Closed 19 years ago

LDAP searches differ when typing in the To: field and when searching for addresses

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

1.7 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jezza, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; INTRANETUSER)
Build Identifier: 

When you search for a person via the Address Book (lets say by typing 
in 'hurst), Mozilla will issue a LDAP search filter similar to:

(|(mail=*hurst*)(cn=*hurst*)(givenName=*hurst*)(sn=*hurst*))

Yet, when you're composing an email and type 'hurst', Mozilla will send the 
following search filter:

(|(cn=hurst*)(mail=hurst*)(sn=hurst*))

Reproducible: Always
Steps to Reproduce:
1. Connect Mozilla to a LDAP server
2. From the main mail window, choose 'Address Book' underneath the Window menu
3. Search for a name
4. Note how many results you get back
5. Now close the Address Book
6. Compose a new email (ensure your LDAP server is your default address book)
7. Type in the same name which you used in the past to search with.
8. Note how many results you get back

Actual Results:  
You will get back potentially far less results than by doing a normal search.

Expected Results:  
When composing an email, you should see the same number of results as when you 
do an Address Book search. At a minimum, the givenName should be one of the 
fields included in the To: field search.

I am using Mozilla 1.7.3. The following are extracts from the LDAP server log 
files:

Within address book:

[24/Nov/2004:14:18:49 +1100] conn=960050 op=1 msgId=2 - SRCH 
base="o=someorg.com,dc=someorg,dc=com" scope=2 filter="(|(mail=*hurst*)
(cn=*hurst*)(givenName=*hurst*)(sn=*hurst*))" attrs="modifyTimestamp 
xmozillausehtmlmail description notes custom4 custom3 custom2 custom1 birthyear 
homeurl workurl nscpaimscreenname c company o departmentNumber department 
orgunit ou title c zip postalCode region st l l street postOfficeBox carphone 
cellphone mobile pagerphone pager facsimileTelephoneNumber 
facsimileTelephoneNumber homePhone telephoneNumber xmozillasecondemail mail 
xmozillanickname displayName cn cn sn sn givenName"
[24/Nov/2004:14:18:49 +1100] conn=960050 op=1 msgId=2 - RESULT err=0 tag=101 
nentries=15 etime=0

From within mail composition window:

[24/Nov/2004:14:20:06 +1100] conn=960085 op=1 msgId=2 - SRCH 
base="o=someorg.com,dc=someorg,dc=com" scope=2 filter="(|(cn=hurst*)
(mail=hurst*)(sn=hurst*))" attrs="cn mail"
[24/Nov/2004:14:20:06 +1100] conn=960085 op=1 msgId=2 - RESULT err=0 tag=101 
nentries=4 etime=0
Version: unspecified → 1.7 Branch
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.