[12518] in Commercialization & Privatization of the Internet
Re: doing something about com-priv
daemon@ATHENA.MIT.EDU (Mark Boolootian)
Fri May 20 03:54:50 1994
From: booloo@framsparc.ocf.llnl.gov (Mark Boolootian)
To: STAPLETON@bpa.arizona.edu (The future Ross Stapleton-Gray)
Date: Wed, 18 May 1994 08:22:57 -0700 (PDT)
Cc: com-priv@psi.com, com-priv-request@psi.com
In-Reply-To: <940518061251.2041b159@BPA.ARIZONA.EDU> from "The future Ross Stapleton-Gray" at May 18, 94 06:12:51 am
>Could com-priv be scrapped and resited on a host that *isn't* flakey?
I don't think psi.com is responsible for the latest debacle. I believe
csn.org was involved in this fracas, and was feeding posts back to psi.com.
We didn't have it all that bad on com-priv. A colleague of mine dropped in
this morning to tell me that he had received 350 copies of a message sent
to the IEEE+MSS list homed at larc.nasa.gov.
However, there is a question I've considered asking for some time: Why is
it that mails frequently queues at psi.com for several hours before being
sent? Delays of five and six hours are not uncommon. Is it that psi.com
is terribly overloaded and is taking that long to process mail?
And why does mail occasionally source from com-priv-forw? In the past few
days, I've received several messages with the From: line set to com-priv-forw
(actually, it might have been the Return-Path: line or Reply-to: line, I
don't recall).
I'd rather not generate a lot of discussion on the list about this, but I'd
sure be interested in knowing why it happens.
>If and when I send out the latest episode of "My Beat is Cyberspace"
>I only want to be flamed by those who object to even a single copy,
>and not by those who've got my bits in triplicate clogging up their
>mailbox...
I'm inclinded to flame for not having received even a single copy...
mb
--
Mark Boolootian booloo@llnl.gov +1 510 423 1948
Disclaimer: booloo speaks for booloo and no other.
