🚀 go-pugleaf

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In fl.config Karl Denninger <karl@fs.denninger.net> wrote:
> 
> In article <AK2C6.19637$FS3.328714@sjc-read.news.verio.net>,
> <admin@mixmaster.shinn.net.no.spam.to> wrote:
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>In fl.config Howard Goldstein <hgoldste@mpcs.com> wrote:
>>> : Again, look at the headers.  These a posts from the Frog remailer
>>> : gatewayed by our mail2news gateway.  
>>> 
>>> I understand.  Getting a handle on the common point of abuse dispersal
>>> works in similar situations however (as for ex. with open wingates,
>>> fucked up DNEWS installs, open mail relays, and the like) You're in an
>>> unenviable position here.  It's likely you don't condone the forgeries
>>> but I don't see how you can avoid responsibility for them by virtue of
>>> their haivng been gatewayed.  It's not clear how they'd get into fl.*
>>> but for the gateway.
>>
>>Any NNTP server that can pass on the posts to the fl.* heirarchy in one
>>simple way.  Regardless, the solution is simpler than you propose.  
>>Report abuse properly, and we'll happily block the forged from: lines.  
>>
>>Aside from someone mentioning this thread to me in a totally different
>>newsgroup, we have never recieved one single complaint regarding this
>>issue and we're more than happy to stop it if someone would only
>>report it.
> 
> Then stop it.
> 
> You know about it, ergo, you can't claim ignorance at THIS point.

Please send the posts with headers intact to 

admins@freedom.gmsociety.org 

and we'll block the e-mail addresses in question.

- -- 
George Mason Society Anonymous Remailer Admin      
PGP Key 1 ID: 0x50A829C9             PGP Key 2 ID: 0x137E3307

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBOtjsuTrfR41zbUFGEQK0NACg+xXJTu+fSPWZAHX2YqaNG6zfp9cAn0FB
+jzem7ccm8hQSrod+vmqo8Xr
=cDh1
-----END PGP SIGNATURE-----