Closed Bug 60764 Opened 24 years ago Closed 14 years ago

[RFE] No folders for newsgroup-filtering (virtual groups)

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Windows 2000
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ammon, Unassigned)

References

Details

Would be great if there were folders to filter newsgroups, so that it is
possible to got all "Music"-related-newsgroups in one folder.
*** Bug 60765 has been marked as a duplicate of this bug. ***
Modifying severity from major to enhancement
Severity: major → enhancement
Summary: No folders for newsgroup-filtering → [RFE] No folders for newsgroup-filtering
Sounds like a request for 4.x type "virtual newsgroups" to me... that idea was
canned early in 6.0 -- not a lot of people used/wanted/needed it even in 4.x.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: esther → laurel
Summary: [RFE] No folders for newsgroup-filtering → [RFE] No folders for newsgroup-filtering (virtual groups)
Assignee: putterman → sspitzer
reassigning to sspitzer
Something that looks a lot like this:

subfolders in newsgroups themselves, so that one can filter all the FOR SALE:
and WANTED: to two different folders in the same newsgroup, for readability. I'd
love this feature!
Maybe it would be a good thing to make this feature more apparent, I didn't know
it was in NN4, and would surely have used it if I did know about it.


It would be nice to have a virtual folder formed with all the watched threads in it.
So you get a tree layout with top level virtual folder "Watched Threads" then a
folder for each group that has a watched thread and then the threads.
this way you can locate the threads that interest you quickly without adjusting
views in all the groups.
Isnt this a dup of bug 11051?
*** Bug 176378 has been marked as a duplicate of this bug. ***
1.: Helge (comment #8), I would say yes this is a dup, except the other bug does
not mention "news" explicitly. Uncertain...
2.: I posted a comment on bug 11051 asking for abolishing per account folder
roots. This would make the user interface a lot cleaner (no separate sent
folders if you do not want them if two accounts are private mail anyways, etc)
and would go together with virtual folders perfectly.
3.: I would like to ask for a feature of *showing* both mail and news in a
single virtual folder, if desired. Elements will be distinguished by their icons
 and Mailnews will offer the right ways of Replying etc depending on the nature
of the message. This would enable us to have a "project related" virtual folder
wich shows the intranet newsgroup assigned to the project as well as personal
mail recieved regarding that matter and a lot of other screnarios alike. Is any
one else interested in virtualising the handling of email and news? This would
place Mozilla a long way ahead of the competition. :)
Should I file a news bug for 3. depending on virtual folders and this bug?


Is there any action on this enhancement bug, since the last message dates back
from 2002-11-17?
I'd really like to see this feature implemented because I have over a hundred
newsgroup subscribtions spread over 5 newsservers. This is highly chaotic, so
I'd like to be able to group them together in folders.
Someone work on a patch.  This is a bug that many people, whether they know it
or not, want fixed.

Should this block bug 11051?

/be
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
Priority: P3 → --
QA Contact: laurel → message-display
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
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
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
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
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
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
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
Ever confirmed: true

    
    

    
  
You can define a saved search for this.
Resolution: EXPIRED → WORKSFORME

          You need to log in
          before you can comment on or make changes to this bug.