Open
Bug 230352
Opened 21 years ago
Updated 3 years ago
check for changed email addresses (do not create redundancy)
Categories
(MailNews Core :: Address Book, enhancement)
MailNews Core
Address Book
Tracking
(Not tracked)
NEW
People
(Reporter: andre, Unassigned)
Details
1) Whenever a new email address would normally be added to the collected
adresses, check first if this email address is already in one of the address books
1.1) if it is not in one of the address books (by email)
1.1.1) check if the values extracted from the from line *1 correspond to another
entry *2
1.1.1.1) if it is not in one of the address books (by values), prompt the user,
show him both entries and prompt him which one to keep or which values to merge
1.1.2) else add it to collected addresses
1.2) if it is in one of the address books (by email), check like in 1.1.1 if
address data differs and prompt the user like in 1.1.1.1
2) else add it to collected addresses
*1 (to be compared to first, last and display)
*2 (that would be eg. a person with exactly the same name, or the same person
with an already created contact and a different email address)
*3 (this could be easily done by duplicating the contact display xul, two
display two contacts side by side, each with a "KEEP THIS CONTACT" button, the
user could then merge all data to his wishes)
Assignee | ||
Updated•19 years ago
|
Product: Core → MailNews Core
Updated•19 years ago
|
Assignee: mscott → nobody
Component: Address Book → MailNews: Address Book
Product: Thunderbird → Core
QA Contact: addressbook
Version: unspecified → Trunk
Comment 1•16 years ago
|
||
I think it would be a better idea to make a rule set that the user can edit.
I would like to check all my address books first and then the Collected Addresses, after that the new e-mail address should be added.
Please be aware that the same address not should be case sensitive but only only look for unique addresses so that abc@def.com, ABC@def.com and ABC@DEF.com not will result in 3 e-mail addresses.
Flags: wanted-thunderbird3?
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•