Reimport mail settings, should display message that accounts already exist

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
--
trivial
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Ninoschka Baca, Unassigned)

Tracking

Trunk
All
Windows ME

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Trunk build 2002-01-07-03:WinMe

Overview: Import Settings from a third party app (i.e. Outlook, Outlook Express, 
Eudora), try importing and nothing happens. Should a message appear stating that 
the accounts already exist?

Steps to reproduce:
1. New profile
2. Start Mail and cancel the Account Wizard, then Exit.
3. Select File|Import
4. Select the Settings radio button
5. Select the third party application (i.e. Outlook)
6. Continue through the import wizard and notice that the accounts are created.
7. Repeat steps 3-6

Actual Results: Nothing happens

Expected Results: A message should appear stating that the account already 
exist since we don't allow duplicate accounts (where the username/servername are 
the same).
(Reporter)

Comment 1

16 years ago
Marking nsbeta1 to offer more information to the user.

Additional Information: Currently nothing happens but the accounts still seem to 
work.
Keywords: nsbeta1
QA Contact: esther → nbaca

Comment 2

16 years ago
reassigning to srilatha
Assignee: sspitzer → srilatha
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P3

Updated

16 years ago
Status: NEW → ASSIGNED

Updated

16 years ago
Blocks: 122274
Keywords: nsbeta1+ → nsbeta1-
Product: Browser → Seamonkey

Updated

11 years ago
Assignee: srilatha → mail
Severity: normal → trivial
Status: ASSIGNED → NEW
QA Contact: nbaca
Summary: Reimport mail settings, display message that accounts already exist → Reimport mail settings, should display message that accounts already exist
Assignee: mail → nobody
Priority: P3 → --
QA Contact: message-display

Comment 3

9 years ago
MASS-CHANGE:
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
Status: NEW → UNCONFIRMED

Comment 4

8 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.