102010 - Warning needed for duplicate Address Book while importing from 4.x

Status: RESOLVED EXPIRED

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

Description

[yulian chang]

20010927 branch build on Window.

When repeatly importing Personal Address Book with new entries in it from 4.x
Communicator, better have warning dialog reminding user that duplicate AddressB
will be created in 6.2.

Comment 1

[Jeff Hooker]

removed tiantian from cc (bad alias; sends mail to jhooker)

Comment 2

[earthsound]

Should this be marked a dup of bug 45946?

Comment 3

[Marco Cimmino]

In Thunderbird 1.0rc1 just importing an Outlook 2003 address book in an empty 
Thunderbird AB results in duplicate entries...I think should be fixed for 1.0 
final.

Comment 4

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420