218466 - autocompletion does not work with LDAP nickname field

Status: RESOLVED EXPIRED

(MailNews Core :: LDAP Integration, defect)

Description

[Seb]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

When i search an address in composing mail, autocompletion does not propose me
Ldap entries having the nickname i write.
Nickname field is filled in address book card with LDAP's xmozillanickname using.
I don't replicate Ldap address book

Reproducible: Always

Steps to Reproduce:
1. In LDAP, define a card with xmozillanickname filled
2. Verify the nickname field is filled in address book card
3. compose a mail and try to find the mail address using nickname

Actual Results:  
The mail address is not found using Nickname.
The mail address can be found using Name

Expected Results:  
The mail address must be propose, as it does with local address book.

Comment 1

[Henrik Gemal]

*** This bug has been marked as a duplicate of 118454 ***

Comment 2

[Seb]

I do not agree with this analyze. This bug may be joined with bug 118454 but is
not the same, as far as i understand 118454
Bug 118454 is about ldap integration in adress book and the fact that ldap
fields like nickname is not "standard" : you need to define xmozillanickname to
feel nickname field in adress book.
In this bug, i defined xmozillanickname, so that i can see nickname field in the
adress book with the xmozillanickname defined in ldap annuary.
So, in this case, the autocomplete search in mail composing should work.

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[Gervase Markham [:gerv]]

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.