70644 - Import "Mail" and Local Folders displays as "Outlook" or "Outlook Express"

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Ninoschka Baca]

Build 2001-02-26-09: NT4

Overview: When importing "Mail", the name of the account assumes the name of the
original email application (i.e. Outlook Express)

Steps to reproduce:
1. Create a new profile
2. When Mail starts cancel the Account Wizard
3. Select File|Import
4. Select the Mail radio button, Next
5. Select Outlook Express, Next

Actual Results: The name of the account that appears in the folder pane is
"Outlook Express".

Expected Results: I'm not sure what it should be called since this account acts
like Local Folders. It is just a holding place for messages and isn't actually
an account.

Question 1: Should it be called Local Folders? 
- This is ok if importing Mail once.
- If importing Mail twice (for instance if you had email from two different
applications, Eudora and Outlook) would all messages be placed in this one area?
This could be more confusing to a user.

Question 2: Should it be a unique name?
- Maybe it should take the name of the ISP such as "Earthlink"? An advantage to
this is that the user is already familiar with this account and its folder
structure. If they imported mutiple "Mail" accounts then each instance could
appear separately making a clear distinction. For instance:

- Earthlink
- Netcom

Comment 1

[Ninoschka Baca]

Marking nsbeta1 so the accounts that are imported have more meaning to the user.

Comment 2

[scottputterman]

resetting priority and milestone.

Comment 3

[jglick]

What import allows you to do is get LOCAL messages (and AB entries) from a 
different mail app and move them into our Mail product Locally.  Is that 
correct?

I would expect that these messages would be grouped UNDER our Local Folders. Not 
as a separate account.  An account wasn't created, just copied local messages 
from a different app.  For example:

Local Folders
   Unsent Messages
   Drafts
   Templates
   Sent
   Trash
   Outlook Express Mail (subfolders within this folder as nec)

Users can then copy/move them as desired.

The last screen of the Import Wizard should tell users where the imported 
messages are: "Your messages have been saved to a folder "Outlook Express Mail" 
in the Local Folders area.  (robin to suggest better wording).

Comment 4

[robinf]

For the message on the last screen of the Import wizard, how about "Your
imported messages have been saved to the folder named <foldername> under Local
Folders." I hope this gets fixed (as described by Jennifer), since the current
UI is confusing. 

Comment 5

[scottputterman]

marking nsbeta1+ and moving to mozilla0.9.1

Comment 6

[(not reading, please use [e-mail] instead)]

giving all my import bugs to chuang

Comment 7

[scottputterman]

moving to 0.9.2

Comment 8

[scottputterman]

moving to 0.9.3

Comment 9

[esther]

no longer nsbeta1+, because new bug written to 86991 is nsbeta1+  and is an
easier fix that will alleviate the confusion.  

Comment 10

[scottputterman]

moving to 0.9.4

Comment 11

[scottputterman]

moving to 0.9.5

Comment 12

[scottputterman]

reassigning to racham

Comment 13

[scottputterman]

moving to 1.0

Comment 14

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 15

[scottputterman]

reassigning to srilatha.

Comment 16

[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 17

[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 18

[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 19

[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 20

[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 21

[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 22

[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