Closed Bug 295050 Opened 20 years ago Closed 19 years ago

should provide ability to filter on Newsgroups header

Categories

(MailNews Core :: Filters, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 178397

People

(Reporter: phil, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412 (KHTML, like Gecko) Safari/412
Build Identifier: 

Thunderbird should provide the ability to filter based on the Newsgroups: header in Usenet postings. 
Services like Gmane crosspost SPAM messages to a special one to ease filtering in the clients. Currently 
Thunderbird only allows post filtering based on Subject, Sender and Date. This should be improved.

Reproducible: Always

*** This bug has been marked as a duplicate of 184490 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Bug #184490 is about IMAP filtering. This bug is about the filtering of Usenet articles. In this mode you 
can't even "Customize" the filter to use custom headers.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
xref bug 178397, bug 178398.  This bug depends on one of those, I just don't 
know whether the Newsgroups header is provided via the HEAD or the XOVER 
command.
Component: Mail Window Front End → MailNews: Filters
Product: Thunderbird → Core
Version: unspecified → Trunk
Well, HEAD provides the full headers (including Newsgroups:) of arbitrary message-ids and numbers in the 
current newsgroups. XOVER lists only headers like Date, Subject, From, Message-ID and some others. 
However as you have to select a newsgroup with LISTGROUP prior to sending XOVER, the group itself is 
known. But yes, you cannot filter on the Newsgroups header just by judging the XOVER output (which is 
probably the one the whole message list is generated of). So Thunderbird should send HEAD requests 
when filtering is enabled.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago19 years ago
Resolution: --- → EXPIRED
Thunderbird does still not allow to filter on the Newsgroups headers, so it's impossible to use it with 
Gmane which crossposts SPAM to gmane.spam.detected. One has to use a real Usenet client like slrn 
instead. Close it if you want but please be aware that this is a serious flaw for some users.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
As the reporter, and as someone who actually followed up and read the referenced 
bugs, you should have marked this as a dupe yourself.

*** This bug has been marked as a duplicate of 178397 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → DUPLICATE
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.