Message-ID filter - help please

Post Reply
willko
Posts: 29
Joined: Thu Jan 22, 2004 4:10 pm
Location: UK

Message-ID filter - help please

Post by willko »

Hi all (alex)

I'm having an issue with the message-id filter.

To demonstrate I've created a basic filter with "hurricane" in the message-id contains criteria. Normally I would use this in negation but for the purposes of the test I'm using it as a select filter. I would normally apply this to is a supergroup (folder) of about 10 multimedia related groups but again for the test I'm using just alt.binaries.multimedia.

When I apply the filter is does catch SOME of the posts,... but not all...? For example, there is a spammer posting with Razor1911 as author who has "hurricane" in message-id and these all show up - but -the poster I REALLY want to block uses powerpost, hence the need for the message-id filter. Here are two examples: S7d5o.12181$zo4.6448@hurricane & 2bd5o.12379$zo4.11255@hurricane that do not show up and therefore are not blocked when negation is applied.

Why is the message-id filter behaving selectively or am I being an idiot about something,.. :?: :roll: :?:

PS - v3 x64 not available anymore?
alex
Posts: 4547
Joined: Thu Feb 27, 2003 5:57 pm

Re: Message-ID filter - help please

Post by alex »

compact binary newsgroup type doesn't normally keep message-ids in RAM, they get washed out shortly to save on RAM usage.

you can just select headers by the author and then delete or purge them, or you can create a kill filter by author so the messages won't even enter the views (but once you need to purge them manually for those headers which are already there).

v3 i pulled off after couple of hours, i had bad connection for about 10 days and couldn't estimate performance gains properly, shortly after release i got contradictory user feedback and decided not to push through if i cannot check it myself, so it will be v3.01. with bypass option for one drive it should behave the same or better (the same when RAM is large enough to have windows file cache always active), with different database and destination drive it is more complicated during unrar, we may have 3 streams (download + unrar read + unrar write) instead of 2 (unrar read + unrar write, while download goes to db drive).
Post Reply