Newsgroups: comp.mail.uucp
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!malgudi!osc.edu!karl.kleinpaste
From: karl.kleinpaste@osc.edu
Subject: Re: UUNET Problems
Message-ID: <1991Jun14.121801.27595@oar.net>
Sender: news@oar.net
Nntp-Posting-Host: ashley.osc.edu
Organization: Ohio Supercomputer Center, Viento Testbed
References: <1991Jun13.104039.2572@tygra.Michigan.COM>
Date: Fri, 14 Jun 1991 13:15:48 GMT
Lines: 28

jp@tygra.Michigan.COM writes:
   What I mean is that it is not a problem with my modem or anything like
   that and I feel that UUNET should take it up with CompuServe. 

Mr Palmer, you've elevated cluelessness to an art form.

UUNET isn't in control of the CompuServe side of their connection to
CompuServe; CompuServe is.  So all UUNET can do, at the very best, is
call them up and relay a small amount of information: "Hi, CompuServe,
UUNET here.  We've got a customer experiencing poor throughput to us
when connecting through your network."  Now, just what exactly is
UUNET supposed to do beyond that point?  Argue with them?  Tell them
to fix their network?  Act as a low-SNR relay between you and
CompuServe about your modem settings, your local access dial number,
your machine setup, etc ad nauseum?

No.  They told you what they know, which is that their end of things
looks fine, and that CompuServe's is broken.  If you want CompuServe
fixed (assuming it's broken; personally, your report is unconvincing),
babble at CompuServe.

It's not UUNET's problem, and UUNET is almost certainly utterly
powerless to fix it.  The problem is yours and CompuServe's -- so
_you_ take charge of the problem, and deal with CompuServe yourself.

Sprinkling "personal responsibility"
bits across the Usenet this week,
--karl
