Closed Bug 543187 Opened 14 years ago Closed 14 years ago

autocomplete selects wrong mail address when composing mail in thunderbird 3.0/3.0.1

Categories

(Thunderbird :: Message Compose Window, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 497722

People

(Reporter: magnusbae, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.78 Safari/532.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; nb-NO; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1

I usually communicate with my coworkers using their company mail, but for some of the Thunderbird has automatically stored their private e-mail after I have replied to those in certain situations. After upgrading to Thunderbird 3, it now has a tendency to select the wrong address. TB2 did not do this. It also chooses addresses that are seldom used where I have contacts with different addresses/similarly named contacts. This was never an issue with TB2, and my contacts addresses haven't changed since I upgraded. The problem is obviously that when I have written mail to these people, I've then accidentally used their private address, which isn't helping in a work environment.

Reproducible: Sometimes

Steps to Reproduce:
1. Make a contact
2. Get an e-mail from a person with the same name, but other address (doesn't have to have a lower alphabetically value either - for instance merete.xxxx@kxxxx.no get's overrun by sctxxxx@hotmail.com)
3. Start typing the name in the "to" box. Use enter to autocomplete when the correct name shows up. 
Actual Results:  
Thunderbird automatically chooses the second address (automatically added) when I write the name of my manually added contact

Expected Results:  
the opposite

It is possible that you have to create the contacts in TB2 and then upgrade to TB3 for this bug to show.
This sounds like a duplicate of bug 497722. Its close enough that I'll mark it as duplicate for now and suggest you retest with 3.0.2 once that comes out.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.