[Coco] Re: UseNet *"Bit.Listserv.CoCo"* NewsGroup elimination

[Stephen H. Fischer]

Hi,

I checked and October 17, 2001 was the date the CoCo list owner posted a
message that the gateway was restored. A previous post stated that he could
not do this as he did not meet the requirements of Princeton to be a list
owner. He said he did with his last post I believe. The gateway was
restored.

My purpose from the beginning was to thank Princeton (and others, but I knew
only about Princeton) for hosting the CoCo mailing list for over 16 years
with  great service. I had never seen or heard about any problems except for
the SPAM which I now know to be an easy fix for the list owner to do. Oh
yes, the gateway closing. The CoCo list owner fixed that and I see that
message in the control archive you provided the location of. Thanks

I felt that not suggesting to Princeton that the list be shut down as it was
only collecting, arching and sending SPAM out would be ungracious to our
host for the great service they had provided the CoCo group for 15 years.

It was quickly pointed out that the newsgroup would go at the same time. And
the quoting of Doom and Gloom continues and continues with more words....

The method that the CoCo newsgroup can, may, will or will not or
cannot....... is of little use unless there is information provided to
assist us in keeping the UseNet *"Bit.Listserv.CoCo"* NewsGroup alive.

What are the actions we can take to insure the continuation of UseNet
*"Bit.Listserv.CoCo"* NewsGroup?

Reading all the rules and required actions which will occur but no one may
actually do and trying to match it up with the UseNet of today is very hard.

Again: What are the actions we can take to insure the continuation of UseNet
*"Bit.Listserv.CoCo"* NewsGroup?

--
Stephen H. Fischer <sfischer1 at mindspring.com>

Michael Black wrote:
> then went to a commerical outfit)
> they stopped rmgrouping.  It seems odd, otherwise, that none
> of the newsgroups have been deleted in recent years.
>
>      Michael