If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

After importing, what account names should appear?

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: Ninoschka Baca, Unassigned)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: imp-mail)

(Reporter)

Description

17 years ago
Build 2001-02-26-09: NT4

Overview: What should the accounts be called after an import is performed?
Should it use the Username, Server Name or some combination?

Steps to reproduce:

- In Eudora, Outlook Express and Outlook I created profiles which included two
accounts (User1 on mail.earthlink.net and qatest33 on nsmail-1).
- In Netscape6 I created 3 different profiles, one for each mail client.
- After importing them into Netscape6, different results occured:

1. Eudora Settings import
- Eudora Settings (should actually reference earthlink)
- qatest33        (uses the username)

2. Outlook Express Settings import (uses the server name)
- mail.earthlink.net
- nsmail-1

3. Outlook Settings import(uses the server name)
- nsmail-1
- mail.earthlink.net
(Reporter)

Comment 1

17 years ago
Marking nsbeta1 because the names of the accounts should be consistent.
Keywords: nsbeta1
QA Contact: esther → nbaca

Comment 2

17 years ago
New accounts created using Mail are now given the default name 
<EmailAddressOfAcct>.  Imported accounts should also follow this if possible.

Comment 3

17 years ago
marking nsbeta1-
Keywords: nsbeta1 → nsbeta1-
Target Milestone: --- → Future
giving all my import bugs to chuang
Assignee: sspitzer → chuang
(Reporter)

Comment 5

17 years ago
The previous statements referenced what appears after Importing "Settings". 
The following statement are about Importing "Mail":

Build 2001-05-23-04: WinMe

Import "Mail" for:
- Eudora, displays "Eudora" in the folder pane
- Outlook Express, displays "Outlook Express" in the folder pane
- Outlook, displays "Outlook" in the folder pane

Build 2001-05-23-08: Mac 9.04
Import "Mail" for:
- Eudora, displays "Eudora" in the folder pane
(Reporter)

Comment 6

16 years ago
Marking nsbeta1 because importing Mail/Settings should reference the account 
name instead of the third party name (i.e. Outlook, Outlook Express or Eudora).

Assigning to Bhuvan, please reassign if this is not correct.
Assignee: chuang → racham
Keywords: nsbeta1

Comment 7

16 years ago
reassigning to srilatha.
Assignee: racham → srilatha

Updated

16 years ago
Status: NEW → ASSIGNED
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P1

Updated

16 years ago
Target Milestone: Future → mozilla1.0
(Reporter)

Updated

16 years ago
Whiteboard: imp-mail
(Reporter)

Updated

16 years ago
Blocks: 126322

Comment 8

16 years ago
Regarding Comment #2

Can this confuse the user?  Consider creating an account username@foo.com [your
current account] ... then importing your mail from Eudora where you used the
same username and servername.   If you strictly adhere to EmailAddressOfAccount
for the imported {folder name} then you could have two of the same name in the
account view.

Perhaps a better name would be {3rd Party Name}:{email address of account} e.g.
Eudora:username@foo.com

This could allow for importing more than one account and not displaying Eudora,
Eudora (2), etc...

Comment 9

16 years ago
nsbeta1- as per ADT
Keywords: nsbeta1+ → nsbeta1-

Updated

16 years ago
Target Milestone: mozilla1.0 → mozilla1.2
Product: Browser → Seamonkey
Assignee: srilatha → mail
Status: ASSIGNED → NEW
Priority: P1 → --
QA Contact: nbaca
Target Milestone: mozilla1.2alpha → ---

Comment 10

8 years ago
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 11

8 years ago
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 12

8 years ago
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 13

8 years ago
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 14

8 years ago
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 15

8 years ago
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 16

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.