312103 - Replying to message creates new Address Book entry when another for that address exists

Status: RESOLVED DUPLICATE of bug 129393

(Thunderbird :: Address Book, defect)

Description

[Anthony]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7

Using Thunderbird 1.0.6 or 1.0.7 (possibly prior versions as well), a new
Address Book entry is created when replying to a message even though an entry
already exists for that user.

For example, this entry already exists:
- First: Fred
- Last: Nerk
- Display: Fred Nerk
- E-mail: [e-mail]
- Additonal E-mail: [e-mail]
- Work: 0123456789
- Home: 0198765432
- Mobile: [phone]

When replying to an e-mail from "Fred Nerk" <[e-mail]> a new
Address Book entry is created:
- First: Fred
- Last: Nerk
- Display: Fred Nerk
- Email: [e-mail]

This example has differences in lettercase, but duplicates are also created
where lettercase is identical.

Reproducible: Sometimes

Steps to Reproduce:
1. Create an Address Book entry:
- First: Fred
- Last: Nerk
- Display: Fred Nerk
- E-mail: [e-mail]
- Additonal E-mail: [e-mail]
- Work: 0123456789
- Home: 0198765432
- Mobile: [phone]

2. Find an e-mail from "Fred Nerk" <[e-mail]> and reply to it.

3. Check the Address Book to see if a new Fred Nerk entry has been created.
Actual Results:  
A new Address Book entry has been created:
- First: Fred
- Last: Nerk
- Display: Fred Nerk
- Email: [e-mail]


Expected Results:  
A duplicate Address Book entry should not have been created. The details should
be considered equivalent to what's already there.

Account type: IMAP (to hMailServer v4.1-B136/MySQL on Windows 2000)

Installed Extensions:
- ConfigDate 0.3.0
- Contacts Sidebar 0.5
- Mozlla Calendar 0.8.3+
- Sort Extensions 2.1
- Sync Kolab 0.4.18

Comment 1

[Mark Banner (:standard8)]

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

Comment 2

[Merlin Cul Kirkpatrick]

To the best of my knowledge this bug still exists in the main code.  To get it
fixed please go to bug 129393 and click the vote button to raise its level of importance.