100336 - Turbo: Quick Launch, conflicts in new profile when creating Mail account

Status: VERIFIED DUPLICATE of bug 99117

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Ninoschka Baca]

Branch build 2001-09-14-03: WinMe

Overview: Using Quick Launch I can get into a state where I cannot create a mail
account. It reports "A mail or newsgroup account with the same user name and
server name already exists. Click Back and enter a different server name"

Steps to reproduce:
1. I have multiple profiles
2. Migrate a profile ([e-mail], nsmail-2)
3. Exit
4. Restart and Profile Manager appears
5. Create a new profile
6. When Mail starts I try to configure it for qatest20 on nsmail-2, basically
the same account.

Actual Results: An error appears "A mail or newsgroup account with the same user
name and server name already exists. Click Back and enter a different server
name". Throughout this process the Netscape icon always appears in the system tray.

Workaround: After step 3, if I exit out of the Netscape icon in the system tray
so Quick Launch is off, then I can configure the new profile for the same mail
account.

Expected Results: If a different profile is used then maybe Quick Launch should
exit and then give the user the option to use another Quick Launch session?

Comment 1

[Ninoschka Baca]

Marking nsbranch becausae Quick Launch to support Multiple Profiles more gracefully.

Comment 2

[lchiang]

cc: trudelle since this is turbo

Comment 3

[Peter Trudelle]

Seth, are you working with ccarlen on this?

Comment 4

[Conrad Carlen (not reading bugmail)]

This is a dup of bug 99117. From that bug:

2. I migrated a profile (qatest20), exited, created new profile (new20) and when
Mail opened I tried to configure it for a qatest20 account. An error appears
stating that an account with this name already exists. This error makes no sense
because this is a new profile with no accounts.

Same story here.

*** This bug has been marked as a duplicate of 99117 ***

Comment 5

[Ninoschka Baca]

Verified Duplicate, sorry about that.

Comment 6

[Tony Tovar]

removing blocker status to bug 75599, since dupes shouldn't block.  Also
confirmed that the duped bug 99117 is still a blocker to 75599.