Closed Bug 257505 Opened 20 years ago Closed 18 years ago

"add to Killfile" button

Categories

(Thunderbird :: General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 10097

People

(Reporter: bobharvey, Assigned: mscott)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Thunderbird version 0.7.1 (20040626)

I would like to see a simple mechanism for creating usenet filters, a sort of
"add to killfile" button.

It should throw up a dialogue that gives you the option to create a filter based on
* from header
* reply-to header
* posting host


In addition, I would like to see filters based on limits to cross-posting, or
for messages whose follow-up is not the same as the posted groups.

Reproducible: Always
Steps to Reproduce:

*** This bug has been marked as a duplicate of 11306 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
whoops, mistyped the bug number.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

*** This bug has been marked as a duplicate of 11036 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → DUPLICATE
*** Bug 285900 has been marked as a duplicate of this bug. ***
I don't agree that this is a duplicate of 11036 - that one talks about the
bayesian filters. this is about a different option. and the bayesian filters
only really handle spam and don't work for usenet.
I agree with Comment #5 - I originally raised this for improvements to the
message filtering, e.g. killfiles, for usenet messages.  As far as I know the
baysien filters don't apply to usenet articles at all.

The usenet filters are still extremely poor compared with venerable products
like agent and turnpike
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
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/
As to auto-resolution, I do not think it appropriate.  The behaviour is
absolutely unchanged in the latest versions, and if you read the contexts you
will see that it was confirmed by more than one person at the time.

If you don't intend to fix it, then fine.  Just say so.
I have stopped using firefox for newsgroup reading, not because it is not very
good - it is - but because there are better products with more sophisticated
killfile systems.
I agree

I had a feeling of not being understood, when this was closed. The bayesian
filters are a) not active for newsgroup reading, b) totally unsuited, as i
cannot specifically ignore one person. And no, the rules don't cute the mustard
either.
This is /not/ a duplicate of Bug 16913.  Bug 16913 has a different scope - it
wants to filter on header lines.  I wanted to do that too.  I also wanted to
filter on posting name, number of crossposts, regexes in subject and reply
headers.  It isn't a duplicate of bug 11036, although that is similar, and it
isn't a duplicate of bug 34973 either.  

But in the end these are all saying the same thing.  We need a filtering
mechanism, or mechanisms, for usenet reading.  (Actually I don't any more.  I've
stopped using Thunderbird for newsgroups a long time ago)
Has this been addressed for 1.5?
Isn't this a duplicate of bug 10097?

Would an offer of a couple hundred $$$ USD to the committer of this feature
help move it along?

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