[Coco] Re: stuff

[John E. Malmberg]

In article <d1078e841115f3035abf9f9357563771 at boisypitre.com>,
"Boisy G. Pitre"  writes:
> Unsubbing my boisy-eD/y2yXejqtZroRs9YW3xA at public.gmane.org address 
> this morning was in order to do some test posting on
> bit.listserv.coco. It turns out that it made no difference whether or
> not I was subscribed to this list, I would get this same email when
> posting to bit.listserv.coco from Google Groups:

I would not expect it to make a difference.

> You are not authorized to send mail to the coco list

<snip>

No one is currently authorized to send e-mail to the coco list on the 
princeton mail server. While the listserv may be still accepting 
subscriptions, the list is set to a "suspended" state until a faculty 
princeton mail server. While the listserv may be still accepting 
subscriptions, the list is set to a "suspended" state until a faculty or 
student of Princeton university agrees to become the owner of the 
mailing list and it's associated newsgroup.

> I forwarded this earlier to Dennis and Rod; not sure what this means,
> but apparently when I post to bit.listserv.coco from Google Groups,
> it tries to send my message over to the mailing list component?

Based on the information you are posting, it looks like google is 
reading the newsgroup property information and sending such posts to the 
parent mailing list as if it were a moderated newsgroup.

That is probably because some of the newsgroups in the bit.listserv.* 
system are read only copies of the parent mailing lists and google does 
not make special cases for the orphans like bit.listserv.coco.

If you get a free encompasserve.org account, you can post to the 
bit.listserv.coco from it through TELNET.  I use ANU-NEWS from there.

You can also reach the gmane newsgroups from there like I am doing now.

> These details are a bit beyond my expertise, and certainly above the 
> time I have to spend on them. Still, resolving these issues would be 
> valuable.

I have posted several times the procedure that is likely to get the 
issue resolved.  So far know one seems to be interested in following it. 
  I do not have the time to do so, or the inclination to become the 
owner of a newsgroup even if that were agreeable to everyone else using it.

The bit.listserv.coco is managed by newsguy.com and they consider the 
owner of the coco mailing list on the princeton.edu server to be the 
owner of the newsgroup.

If you want to do anything with the newsgroup other than let it run on 
auto-pilot until someone else does something, then you need to get the 
"ownership" of the bit.listserv.coco transferred to someone else.

I expect that newsguy.com would only accept princeton.edu's request for 
a change of ownership since princeton.edu is the current owner of record.

Once that is done, it appears that newsguy.com will gate the newsgroup 
to what ever mailing list that the new owner requested.  I suspect that 
they can enable the moderator function to the new owner which would be 
useful if they can set up a server to auto-approve most posts, and 
divert the questionable ones to a set of humans.

My prediction is that nothing will change, and that this whole 
discussion will be repeated about 6 months time.

If you check the archives of this forum, you will find that all of this 
has been discussed before, and the last time I posted more detail and 
many of the URLs that back up what I posted.

-John
wb8tyw(at)qsl.net
Personal Opinion Only