Closed Bug 161051 Opened 22 years ago Closed 14 years ago

Open a tab for each folder receiving new mail

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: treebeard, Unassigned)

References

(Depends on 1 open bug)

Details

Eudora does this.  It is the only feature I miss moving from Eudora to Mozilla.

For those who haven't used Eudora:

you click the icon to "get messages"
When the filters place an incoming mail into a folder/sub-folder,
a new tab with the folder name appears along the bottom ( I don't think 
it matters whether it's the bottom or the top )

These tabs remain open until closed.  They even remain open between sessions.

When you select a tab, it's contents comes to the foreground.  Selecting an
individual email opens it in it's unique tab with a different icon and the
"from", subject as the tab label ( actually just the first so many characters
not a dupe. see also bug 87520
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: open a tab for each folder receiving new mail → Open a tab for each folder receiving new mail
QA Contact: olgam → laurel
*** Bug 188680 has been marked as a duplicate of this bug. ***
Blocks: eudora
Depends on: 196760
OS: Windows 98 → All
Hardware: PC → All
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: laurel → message-display
MASS-CHANGE:
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
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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.