83775 - Ability to share folders among accounts

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Dwayne]

Build 2001-06-01-04, Win2k sp2

Behavior:
I have two POP accounts, and I notice there are draft/template/sent/trash
folders for each account.  Are these necessary?  Only one outgoing mail server
is defined.  IMO, these should be shared folders for all accounts.  It's also
debatable whether or not the inbox should be shared as well.  This is currently
how Outlook handles it (yuck, I said the O-word).

So we should make it a user option whether to share an accounts folders with the
main set or create an individual set for that account only.

Example case:
Say I have 3 accounts (god forbid).  The first two accounts have the same domain
but different user names, and I want them to share folders (i.e. work email). 
But say I also have another account (i.e. home email) that I want to check as
well, but don't want them to be combined with work email.  So for that account,
I would have it create its own, unshared folders.  I would thus have two folder
sets.

But if I have two home accounts at home, I only want one folder set to appear
since, IMO, they should be combined.

One more thing, what exactly is the use of the Local Folders folder?  To me,
this is just a third copy of unused folders.

Comment 1

[Dwayne]

I know this has little priority right now so sorry to add more to the mix...

I realized I didn't update the OS/Platform to all, so changing.

Also changing severity to minor for now.

Comment 2

[Keyser Sose]

Marking NEW changing severity and description.

Comment 3

[Ian Brandt]

Hi,

I'm a recent convert from OE (the new Bayesian spam filters won me over), and I
also do have 3 POP accounts.  I am looking forward to this RFE very much.  I
just wanted to add that I definitely would appreciate the option of having
separate inboxes for each account, even if the other folders are shared.  In OE
I created these using user defined folders and filters.  I suppose I could do
the same in Mozilla, but there is one catch: the inbox is a "special" folder in
that it can't be deleted.  In OE I once accidentally deleted one of my user
defined "inbox" folders when I meant to delete just one of the messages in the
folder (I find it easy to mix up whether the folder or the currently displayed
message has the focus in the three pane model).  Then of course I emptied the
trash before I realized what I had done.

I personally only care to have the option of excluding the inbox when sharing
folders in multiple accounts, but perhaps other users would want to be able to
exclude other pre-defined folders as well?  It might be very slick if you could
arbitrarily exclude a folder via that folders properties dialog.  An excluded
folder would just be prepended with the account name.  If one were to exclude
the Inbox and the Templates folders it would look like so:

- Mail
  - Home Inbox
  - Home2 Inbox
  - Work Inbox
  - Unsent Messages
  - Drafts
  - Home Templates
  - Home2 Templates
  - Work Templates
  - Sent
  - Junk
  - Trash
  - MyArchive

I am not sure though how you would integrate this suggestion with Dwayne's of
being able to merge the folders of some accounts but not others?. . .

- Mail
  - Home & Home2 Inbox
  - Work Inbox
  - Unsent Messages
  [...]

Regards,

Ian

Comment 4

[R.K.Aa.]

dup of bug 30057?

Comment 5

[matt haines]

i've gotta vote for reducing the mailbox/folder clutter too. i've got FIVE accounts i check regularly, 
and each one of them has a trash, a templates folder and a drafts folder (not to mention in box). 
this is excessive, because they don't get used! i have the option turned on to store drafts and 
templates in the 'local folders' version of these. if you've got two accounts maybe it makes sense, 
but i can't even see the entire list of folders on my 19" monitor!

Comment 6

[Ling Li]

I guess bug #208443 is similar to this one.

Comment 7

[Scott MacGregor]

please don't plus bugs for the release. That is the job of the delivery teams.
Doing so may cause you to lose your bug priveleges.

Please use a global inbox if you are a pop user and you only want one set of
folders. 

Comment 8

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

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

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

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

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

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

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

[:Hb]

SM did get the Global Inbox feature.