[news filters] allow for news filters on more XOVER fields once biug 17483 is fixed, we will be able to filter on sender, subject and date. we also get the message-id, size, reference, and lines info on the XOVER line. I theory we could make it so the user could filter on that too. this is way future, if we decide to do it at all.

Size and/or line count, in particular, would be very useful for those on slow and/or pay-per-minute connection, e.g. to filter out binary spam to non-binary groups.

Allowing filtering on any header, like it is for mail, would make a lot of sense for news. An example is filtering cross-posts, or filtering Usenet posts from a specific host or domain.

Alex (tech_dev@wildintellect.com) writes: I just wanted to add that it would be good to filter based on the Xref header and/or the Newsgroup field. Gmane.org one of the largest news readers for the open source community uses these fields to flag spam on it's lists. Documentation here http://www.gmane.org/filter.php Examples; Newsgroups: gmane.comp.web.zope.plone.website, gmane.spam.detected Xref:news.gmane.org gmane.comp.web.zope.plone.website:658 gmane.spam.detected:1908545

Filter on "Nobody_NScomTLD_20080620"

Most of what's requested here already works (on trunk). Specifically I checked that Message-ID, References and Lines work when added using Customize. Size (KB) is already available by default. Newsgroups and Xref should work, too. The only thing left here is that headers added using Customize only offer "contains", "is" and "begins/ends with". It would be helpful to also/instead have "is greater/less than" for headers like Lines, though. Maybe we should morph this bug into that because the rest has been dealt with in bug 16913.

(In reply to comment #5) > The only thing left here is that headers added using Customize only offer > "contains", "is" and "begins/ends with". It would be helpful to also/instead > have "is greater/less than" for headers like Lines, though. Maybe we should > morph this bug into that because the rest has been dealt with in bug 16913. We can handle any header, but that doesn't mean we save ourselves the effort if it's already processed by XOVER in certain cases--Xref is one that comes to mind (I special case Message-ID and References). Lines probably needs to have its own header as well (not in the customize bar). And, theoretically speaking, if someone has a custom OVERVIEW.FMT, we'll be doing incorrect stuff up the wazoo.