Closed Bug 330757 Opened 19 years ago Closed 16 years ago

address autocompletion ignores secondary mail attribute for LDAP directories

Categories

(Thunderbird :: Address Book, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 261497

People

(Reporter: bob, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 I have a LDAP directory configured as address book. I noticed that when I create an address book card in my local personal address book and I specify an address in both the primary and secondary email address fields that autocompletion displays both addresses when I type the first few characters of the person's name. This is what I expect. But for an LDAP directory the secondary email address does not show up when I type the first few characters of the person's name. Reproducible: Always Steps to Reproduce: 1.Configure a LDAP directory 2.Verify a given person in the directory has a secondary email address defined. 3.Open the compose window and type the first few characters of the person's name. Actual Results: Autocompletion does not display the secondary address. Expected Results: Display the secondary address like the personal address book does. In my particular case my backend directory is an openldap server and I have the following statement in my prefs.js file to retrieve and display the secondary mail attribute which in my case is othermailbox: user_pref("ldap_2.servers.default.attrmap.SecondEmail", "othermailbox"); When I use the access the advanced address book search window for this directory and select search for a person I know has a secondary mail address the additional email column properly displays this attribute in the search result. However, when I do a search specifying the additional email field to search on, the entry I expect is not returned. I don't know if this issue is related or not.
Maybe related to Core bug 262093 or Core bug 261497?
This may the same problem as in bug 314047, for which I just supplied a patch. If your local address book has autocompleteToMyDomain set but the LDAP address book doesn't, that would lead to the popup incorrectly being suppressed for the two addresses displayed for the LDAP address book, but not for the three addresses (two + one for your domain) displayed for the local address book.
This appears to be the same as bug 261497, and possibly bug 262093 as well. Resolving as a duplicate of the earlier one.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.