🚀 go-pugleaf

In message <1bL1R$CuL095EAji@jsunderwood.demon.co.uk>, John Underwood 
<john@jsunderwood.demon.co.uk> writes
>On Wed, 25 Oct 2000 at 19:40:28, Jim Crowther <tpalpha@crowfam.org.uk> 
>wrote in :
>(Reference: <yDBI5hFcky95EAig@crowfam.org.uk>)
>
>>Cross-post to d.i.s.t added.
>>
>>In message <01c03e81$3390ba00$04245cc3@generix4>, Jason Batley 
>><jason@generix.ltd.uk> writes
>>>Hi,
>>>
>>>I am relatively new to newsgroups and would like advice on the following.
>>>
>>>Is there any software available that can sit on our NT server, scan
>>>selected newsgroups for headers with certain keywords in them and then
>>>distribute to the according product specialist within our office via
>>>internal email?
>>>
>>I may be wrong, as I have not tried this, but I am 99.99 per cent 
>>certain that Turnpike will achieve the result you want, with the 
>>exception that the articles remain as news on the workstation.
>>
>>This follow-up is cross-posted to demon.ip.support.turnpike.
>>
>
>I haven't done it, but I don't think it would work the way Jim or Jason 
>describe. However, you might be able to do it by carefully written 
>rules for the individual users. I can see how it might be done for 
>mail, but I have no idea how with news.

I am fairly sure each user can set their own kill rules, and a custom 
rule can be set to accept, with all the finesse of custom rules...

>What Turnpike does, which may be in the direction of this is collect 
>the news centrally, but allow all users their own views of it. One 
>reader can mark a message interesting and to be kept, another can mark 
>it uninteresting, they both have their own independent markers of which 
>articles they have read.
 >
I hope I've not missed something obvious, but I'm sure an accept rule 
placed before a reject will accomplish what Jason wants for individual 
users.

Someone somewhere is bound to know different...

-- 
Jim Crowther           "It's MY computer" (tm Steve Gibson)
Mailto:jim@crowfam.org.uk
Public PGP keys at ldap://certserver.pgp.com (and the rest)
Key ID 0xAEEDBEEE (DH/DSS 2048/1024), 0x6FD7CF8F (RSA 1024)