Closed Bug 130613 Opened 23 years ago Closed 23 years ago

Auto collection of addresses doesn't filter out unqiue entries

Categories

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

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: rufwork, Assigned: racham)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031104

Collected addresses option in Preferences-Mail & Newsgroups-Addressing will
continue adding the same emails to your address book with each email sent and/or
received (depending on the selections in the "Email Address Collection" section
of the preferences).

Mailing lists do the same thing -- the names will be duplicated with each use of
the mailing list, making the list send out duplicate copies of each email, the
number of duplicates increasing by one with each use and starting with 1
duplicate (2 total) with the first use.

Reproducible: Always
Steps to Reproduce:
1.Receive email
2.Entry duplicated

1.Use mailing list when addressing an email
2.Multiple copies are sent

Actual Results:  Multiple emails were sent and multiple entries appeared in the
Address Book

Expected Results:  Only one entry per unique email address should be entered
into the address book.  Mailing lists should have one copy of unique email
addresses only.

*** This bug has been marked as a duplicate of 45946 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
This is not a dupe of bug 45946, that bug is about duplicate entries added by 
hand whereas this bug seems to be a combination of two bugs that have received 
attention lately (the mailing list duplication and the CAB duplication).  It 
probably is a dupe of something, but the mailing list duplication at least has 
another open unconfirmed bug, and this bug could be useful for it.  Reopening.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Okay, so I've finally found the time to investigate this (there are a number of
bugs on this subject).  The bug is a dupe of both bug 120665 and bug 121478
(which was fixed, but that fix was only checked into the trunk and not 0.9.9);
I'm marking it invalid, since it talks about more than one problem, but really
it's so I don't have to choose :-)
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → INVALID
Verified Invalid.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.