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

There should be separate "Unsent" folders for each account

NEW
Unassigned

Status

MailNews Core
Composition
--
enhancement
12 years ago
9 years ago

People

(Reporter: Norbert, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [penelope_wants])

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.12) Gecko/20050920 Firefox/1.0.7 SUSE/1.0.7-0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.12) Gecko/20050920 Firefox/1.0.7 SUSE/1.0.7-0.1

I'm one of these users who prefer to have seperate folders for each account. This means that I don't use "Local Folders".

But if I click "File/Send Later" in the Compose window, the mail is saved in "Local Folders/Unsent", instead of current account/Unsent.

It looks like only Local Folders has a subfolder "Unsent".

Reproducible: Always



Expected Results:  
Seperate "Unsent" folders for accounts with dedicated mail folders (such accounts that are not stored in "Local Folders".

Updated

12 years ago
Severity: normal → enhancement
Hardware: PC → All
Version: unspecified → Trunk
(Reporter)

Comment 1

12 years ago
In my opinion this is a defect, not an enhancement.

Because although I have UNCHECKED the option
"Use Global Inbox (store mail in Local Folders)"
while adding my eMail acounts, Local Folders is used.

Comment 2

12 years ago
Related to Suite bug 129260 or maybe Suite bug 25428 comment 5?

Updated

12 years ago
Depends on: 129260

Comment 3

11 years ago
+1

Updated

11 years ago
Blocks: 362057

Comment 4

11 years ago
Change to confirmed?

Comment 5

9 years ago
It looks like either bug 129260 should get resolved as WFM, or this one should get marked as a DUP of that one if it stays open.  wsmwk: any preference?
1. There was discussion elsewhere about how unsent should work going into thunderbird 3. Perhaps it was only in the context of making ALL messages go to the unsent folder, to make send async (one of davida's ideas). Can we find that discussion + bug(s)?

2. iirc the direction was to rename unsent to outbox and have a single outbox, in which case this bug and 129260 likely become WONTFIX.

3. someone should probably look into what penelope/eudora are doing if it isn't already part of #1 above.
Assignee: mscott → nobody

Comment 7

9 years ago
(In reply to comment #6)
> 1. There was discussion elsewhere about how unsent should work going into
> thunderbird 3. Perhaps it was only in the context of making ALL messages go to
> the unsent folder, to make send async (one of davida's ideas). Can we find that
> discussion + bug(s)?

In current trunk code, there are 3 mailboxes being used:

- Drafts: Saved outgoing messages that have not been marked to send later
- Outbox: Messages marked to send later
- Sent: Messages that have already been sent

Drafts and Sent are per-account, and there is a single Outbox in Local Folders.


> 3. someone should probably look into what penelope/eudora are doing if it isn't
> already part of #1 above.

We don't have any plans in Penelope/Eudora to muck with this.  Classic Eudora has only one mailbox for all of this: "Out".  All saved drafts, messages to be sent later, and sent messages are stored there.
In the Folder Pane bug ( bug 446306 ) we plan on only having one Outbox.  Though we'll allow for people to view the separation of outbox mails from different accounts if there exists multiple outbox emails.  So part of this request would be fulfilled in the new approach but I can't see implementing this in the current code.
No longer depends on: 129260
Status: UNCONFIRMED → NEW
Component: General → Composition
Ever confirmed: true
Product: Thunderbird → MailNews Core
QA Contact: general → composition
Summary: There should be seperate "Unsent" folders for each account → There should be separate "Unsent" folders for each account

Updated

9 years ago
Whiteboard: [penelope_wants]
You need to log in before you can comment on or make changes to this bug.