Closed Bug 84503 Opened 24 years ago Closed 24 years ago

Autocompelete against LDAP doesn't hold

Categories

(MailNews Core :: Composition, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 81695
mozilla0.9.1

People

(Reporter: esther, Assigned: bugzilla)

Details

(Keywords: dataloss)

Using builds 2001-06-07 on win, mac and linux if I autocompele on a name from the LDAP directory, the autocompleted name changes to the first on one the list after <Enter> to accept or pressing <Enter> to move to the next field. 1. Launch App (have LDAP set up to autocomplete against AOL/TW directory. It doesn't matter if you have the checked or unchecked for "If there is a match in your local address books:" option. 2. Bring up a New Msg window and type in a name that you know will match something in the LDAP directory. I used "Nav" . 3. When autocomplete comes up select a name that you know is coming from the LDAP search, notice it displays in the To: field. Now press <Enter> Result on Win & Linux. The name changes to the default name+domain (which is the first one on the list) Result on Mac, the name displays in the To:field, but when you press <Enter> again to go to the next field the name you typed above changes to the default name+domain. this is really bad, user can send mail to recipient they never intended to send to.
nominating nsbeta1 and dataloss
Keywords: dataloss, nsbeta1
QA Contact: sheelar → yulian
I have also see this on today's windows build. I opened the compose window and started to type an email address and the auto complete kicked in but selected the wrong name. So I went down the list and picked the one I wanted and selectec it. I was now in the address field. I then went to the message pane and then noticed that the first email address replace the one I had selected.
paul - do you have ldap set up?
cc'ing dmose and hewitt. Putting on 0.9.1 radar.
Priority: -- → P1
Target Milestone: --- → mozilla0.9.1
Paul, are you using LDAP too?
I talked to Paul at the time and he told me he was using LDAP. His scenario was the same as mine, however he didn't catch the name change before he sent.
This is a dup of 81695, which is awaiting comment from ducarroz and/or hewitt on possible solutions. *** This bug has been marked as a duplicate of 81695 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
This bug occurs only if you have both Adressbook and LDAP autocompletion enable. Looks like we are doing something wrong when we merge the result from both source!
verified dup
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.