Usenet Explorer

Hi there,
since I decided to reorganize some filters, I found some issues,well there are old but I was too lazy to report them.

1 - first one is the "inheritance" filter :
If you put an initial filter on the default newsgroup every virtual/folder or simple newsgroup will have that filter if left with "default" as initial filter and that sounds quite right.
Again if you put a initial filter to a simple newsgroup to "none" that still works the way it supposed to.
But if you set a virtual/folder to "none" as initial filter it will still have the default filter from the default newsgroup even if you set all his "child newsgroups" to "none", that's where it seems wrong.

2- second one are the watch and kill filters:
For what I understand, it seems that those filters only apply to single messages, thing I can understand.
But using a "messages are collections/auto collections" in a watch filters will do nothing interesting though nothing stops you to use it.

Recently, there was some tv imposter posts that could use a kill filter based on message-id since author and subject were insufficient.
Somehow after using a "message-id contains something" it only killed the single messages (par2 zero, sfv and nfo) and let the partial messages live.
Of course you can use the "Header kill filter" in "Articles" pane that can be very specific but it seems more elegant to use a kill filter (yeah kill all those s*ckers! ) than having ue downloading and aborting articles.

Well I'm just saying hey I don't know, that's weird.

watch filters work on incoming headers, so they are applied to the stream of headers, no collections there around as separate entries, maybe what you mean is something like "message belongs to a collection", that could maybe work, a problem here is the very first file of the collection is not yet counted as collection, so some files would need be processed with "delay".

as to the kill filters it should work, don't include angle brackets into the expression since UE takes message-id without them, also are you using properties->kill filters? - there is no difference between single and partials for kill filters since they work on parts. e.g. i made the killl filter "*" and nothing came through, so it appears to work. as to view filters (when you apply a filter to limit records in a view) there is no such thing as message-id of a partial message.

with the folder "none" and "default" i'll check it out.

Yeah, I'm using the "properties->kill filters".
I decided to try a new database with minimal setup.
With a "message-id contains *" as kill filter I ended up with only par2 zero, sfv and nfo files being affected.
Then it hit me, I use the default settings "Mark deleted" for the kill filter.
If I switch to "Discard completely" it does work as it is suppose to !
Any way you could check for the "Mark deleted" option too ?

I doublechecked, when it is discard option it works on the parts level before headers enter the database (even before checking the message is single or partial), when delete headers option - it works on the single/partial as a whole (and a partial doesn't have message-id).

Even as maybe noone else will need it - here the call replaced with one on the part basis, for practical purposes there are no difference in other regards:

http://www.netwu.com/ue/test/ue+.rar

Working great, thanks.