At 08:58 PM 5/10/01 -0700, you wrote:
>I know you're more than booked with requests for new features and bug
>fixes. But here's one that I'd like to throw onto the table for
>consideration.
>
>Currently when a spammer is detected, the admin must add a spam keyword
>to the filter mechanism (external, or internal). But typically by the
>time you know about the new spam, the spammer has hit a large number of
>groups with a large quantity of posts. Attempting to track them down
>individually is out of the question. And the only way I know of to have
>DNews "re-filter" the database is to do a pile rebuild (which takes
>hours). A side effect of the pile rebuild is that it is confusing to the
>clients while it is running, since posts vanish and reappear as the
>rebuild performs. And, news feeding stops while the rebuild runs.
>
>What I would dearly love to see is a "tellnews re-filter" which would
>trigger a background task to run at a low priority, in conjunction with
>normal DNews operation. The result would be to re-filter all posts with
>the current anti-spam definition(s). Since there is no need to run this
>at a high priority, it could run at an extremely low (idle?) priority.
>The effect would be to mark posts as "deleted" and not actually delete
>them (requiring a rebuild).
>
>It would be possible to build this as an external utility. And if you
>indicate that such a new command (feature) is not doable given your
>schedule, I'll consider doing it as an add-on utility. But I truly think
>such an ability would be strongly desirable, given the amount of Usenet
>spamming.
I'll put it on the todo list, but can't promise when it will appear.
ChrisP.
