User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 If you use an email address which was entered in the Additional Email text field of a users card to add into a list, a second card is generated for that same user. Reproducible: Always Steps to Reproduce: 1. In Address Book, create a New Card for Jon Doe. 2. Add a primary email address email@example.com. 3. Add a secondary email address firstname.lastname@example.org and save it. 4. Now create a new list and enter the secondary email addres to the list. Actual Results: Once the list is created, a second card is created for Jon Doe using the secondary email address as the primary email address now. Expected Results: Should not have created a second card for the same person since the email address was already entered in the Additional Email field of the original card.
not going to get to this for 1.0
TB 2.0 Bug still exists. Reproducible: Always
I'm confirming this on TB 2.0 also.
This additionally address card cannot be deleted. Following js error appears: Error: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIAbView.deleteSelectedCards]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://messenger/content/addressbook/abCommon.js :: AbDelete :: line 358" data: no] Source File: chrome://messenger/content/addressbook/abCommon.js Line: 358 Removing target milestone because TB2 is already released. Scott, could this be a blocker for Thunderbird 3?
After downloading my adressbook from GMX to TB 2.0 I had the same problems. I'm not firm in programming TB, but I want to recommend following general solution: The entity "mailing-list" shoud consist of (at least) three fields: 1. the key (name) of the mailing-list, 2. the unique key for the contact in the adressbook, 3. a field for the name (not the content !!!) of the "e-mail-field" in the contact-file, which shall be used for this contact in this mailing list. The program to define the content of the mailng-lists had to be changed for a function to select the wanted e-mail-field. The programms using a mailing-list had to be changed, that they read for every row of the mailing-list in the contact the actual e-mail-adress from the defined field. So it wouldn't be necessary to store a incomplete copy of a contact for this reason. The data woudn't be redundant! If the e-mail-adress ( e.g. private) or the second e-mail-adress (e.g. corporate) would be changed, all mailing-lists will use beginning from this moment the updated e-mail-adress. There wouldn't be a copy of a contact or a row in a mailing-list with an invalid mailing-adress. The data would be integrety!
Bug present in latest nightly on OS X (Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:220.127.116.11pre) Gecko/2008062403 Thunderbird/3.0a2pre ID:2008062403). This one has been bothering me for a long time now. TBird needs better handling of alternate email addresses; it would be nice to be able to list more than one alternate as well!
Could this bug somehow be fixed with the upcoming address book changes?
(In reply to comment #7) > Could this bug somehow be fixed with the upcoming address book changes? > It has potential to be yes. The restructuring should affect how mailing lists are generated and maintained. Until we get further down the line I can't say much more.
Not a tb3 blocker, moving to wanted P3.
Nightlies still don't match additional email field when attempting autocomplete. I don't think it makes any sense at all to even have an additional email field in the address book if it isn't recognized by the program. I personally feel that this is indeed something that should be addressed for TB3, not put off. The bug has been present since 2004, through two major versions; should it really be there for a third version? Performance for the additional email field has actually degraded in my experience since TB2. Pretty sure it used to be brought up for autocomplete, but it no longer even does that.
(In reply to comment #10) > Nightlies still don't match additional email field when attempting > autocomplete. I don't think it makes any sense at all to even have an > additional email field in the address book if it isn't recognized by the > program. You're thinking about bug 447927 please don't confuse bugs with comments about different issues.