Closed Bug 211622 Opened 22 years ago Closed 21 years ago

address book allows user to save exact duplicate email addresses.

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 45946

People

(Reporter: joe, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

If you happen to save an email address that is an exact duplicate of an existing
address entery.  Mozilla does not give you a warning and ask if you really want
to do this.  Instead, Mozilla goes ahead and enters the exact duplicate entry.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
duplicate of existing address entry gets put into address book.

Expected Results:  
Mozilla should say that what you were adding to the address book was a duplicate
and ask if you really want to do this.  In past Netscape (and I think Mozilla)
edition,  If you UPDATEed an existing name with a new email address,  you would
get an WARNING that there was a similar entry and asking did you wish to replace
it or add this second entry leaving the old.
I believe my problem is related to this one.
To create duplicate entries...
1) Add e-mail address to Address Book.  (ex.  Name "Johny", Email "jsm@xyx.com") 
2) e-mail "Johny" and have "Johny" reply.
3) Suspose "Johny" replys and his profile is setup as
   "Smith, John"  jsm@xyx.com
4) Reply to "Johny"'s reply.
5) A new Address book entry is added with Name "Smith, John", Email "jsm@xyx.com")

I don't want a new entry for "jsm@xyx.com".  I want to keep the one I have and
leave the name as "Johny".
This is a dup of bug 45946.

If only I had the power to mark dups...*sigh*

*** This bug has been marked as a duplicate of 45946 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.