Xref: utzoo news.admin:3558 news.groups:5484
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!mcnc!ecsvax!bch
From: bch@ecsvax.uncecs.edu (Byron C. Howes)
Newsgroups: news.admin,news.groups
Subject: Problem sites, Problem sysadmins
Message-ID: <5422@ecsvax.uncecs.edu>
Date: 26 Sep 88 18:25:44 GMT
References:  <3147@utastro.UUCP> <699@mace.cc.purdue.edu> <1581NMBCU@CUNYVM> <828@acer.stl.stc.co.uk> <2067@looking.UUCP> <4910@juniper.uucp>
Reply-To: bch@ecsvax.uncecs.edu (Byron C. Howes)
Organization: UNC Educational Computing Service
Lines: 25

In article <4910@juniper.uucp> yelorose@juniper.UUCP (Bob Mosley III) writes:
>...this brings up a good point: If the admin of a particular problem site
>refuses to take action and supports its problem users, what recourse is
>there? With all the problems coming from Portal, there must have been some
>sort of procedures set up to dispose of them accordingly.

I'm not going to join the ranks of the Portal bashers.  Whatever sins
the users at Portal may or may not have committed they have been drowned
out in both annoyance and cost by the responses.  Portal's biggest
problem seems to be an arrogant bureaucracy that informs neither its own
users nor its fellow sites.

Still, the obvious way to deal with a problem site is to cut them off
the net.  The place to apply pressure is to those sites who exchange
mail and news with the offending site.  I daresay that an instransigent
sysadmin is going to pay attention when his news and mail feeds threaten
to cut him off.

I would have thought this was obvious.
 

-- 

Byron C. Howes			    Computer Systems Manager
bch@uncecs.edu			UNC Educational Computing Service