Usenet Explorer

Hi all,

Err, I suppose this pertains primarily to binary postings... But then again sporging is everywhere now...

I'm not bad with the filter editor & I understand boolean but...
I cannot find a way to filter on the poster's IP address?
I have entered offending IPs into Header Kill Filter but this only prevents downloading of said items.

Also I have heard of people using proxy services...

Any suggestions?

it is in the article pane, header kill filter, it is applied only to incoming article bodies (when downloading headers the info cannot be retrieved without significant performance impact)..

Thanks for the reply Alex, I understand the re: performance impact .

I suppose this is a "development" style question.... but..

Is there any way to incorporate a "All Header Fields" type option in the Filter Editor condition section? Perhaps just a general sweep of all headers for a few known IPs and a ban setting...? I'm assuming this would not impact the header retrieval but would allow for a particularliy heavily spammed group to then be filtered after all the headers were retrieved..? (e.g. a.b.w.imb-pc.0-day)

Thanks so much for creating Newspro Alex, it is, without doubt, the best newsreader ever.

did you ever find a way to filter out on NNTP-Posting-Host?

if anyone has been on any of the binary groups within the last couple of weeks then you will have noticed quite a lot of mass flooding post's, they are starting to get tiresome, but they are all posted from the same 3 - 4 NNTP-Posting-Host

is there a way to filter these out with NewsPro, ive successfully managed it with xnews but i dont use xnews all the time, im kinda hoping there is a way with NewsPro as well

these are the posting host's IP's

24.166.4.18
24.71.223.147
66.25.253.7

any and all help appreciated

at the time of downloading headers the posting host is not known (unless to download through very slow method, but it is impractical).

so the only option is to prevent downloading bodies from these servers in properties->articles, header kill filter

thats the problem, everythin about these post's are different, the only things which are the same are the NNTP-Posting-Host and the server which they posted through

hmm ok, just had an idea, since NNTP-Posting-Host is not a standard XOVER header i can use nfilter to filter that out, not the best solution but at least it will work...and the answer was in front of me the whole time