🚀 go-pugleaf

In article <Pine.A41.3.95.970116104753.25432A-100000@archa6.cc.uga.edu>,
William Young  <will@arches.uga.edu> wrote:
>I think we're all painfully aware of the glut of spam in the ahn.*
>heirarchy. Why don't the University, the local ISPs, et al allow a single,
>known spam canceler "Cancel Moose". Anyone (especially using free agent or
>GNUS) can forge a cancel message, removing the spam from the group, and
>then sending an official complaint to to the luser's provider. Even if
>this didn't stop the attempted spamming, ahn.t.l and a.g would become
>usable groups.

Most of the spam that hits ahn.* groups *is* being cancelled.  
Unfortunately, because ahn.* is so early in the alphabetical list of 
newsgroups, the cancels don't kick in before the spam reaches ahn.* 
groups.  Most of the recognized cancellers use early alt.* groups to pick 
up on spam; ahn.* precedes alt.*, so we're in a pickle here.

Note to all: please do NOT just decide to start issuing cmsg's on your 
own.  Read the news.admin.net-abuse.* groups for a while, post there, and 
learn the system.  There are already several people whose cancel messages 
are widely accepted, because they are known entities and trusted.  Rogue 
cancellers cause problems.  Please don't become one.

Ahn.* has a naming problem.  I don't think any of us realized what an 
issue it would be, back when we started talking about it.  Certainly, to 
be usable these sad days, a group needs to follow alt.* in the alpha list.

Crossposted to ahn.general, since I don't read it but this affects it.

-- 
_________________________________________________________________________
Kate Wrightson          |
kate@rigel.econ.uga.edu |  
blaze.cba.uga.edu/~kate |