Re: Restricting the list

Roger Fajman <RAF@cu.nih.gov> Tue, 06 February 1996 02:20 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14413; 5 Feb 96 21:20 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14409; 5 Feb 96 21:20 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa19535; 5 Feb 96 21:20 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id VAA23000; Mon, 5 Feb 1996 21:19:57 -0500
Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.111]) by list.cren.net (8.6.12/8.6.12) with SMTP id VAA22929; Mon, 5 Feb 1996 21:18:26 -0500
Message-Id: <199602060218.VAA22929@list.cren.net>
Date: Mon, 05 Feb 1996 21:16:21 EST
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Roger Fajman <RAF@cu.nih.gov>
To: conklin@info.cren.net, ietf-smtp@list.cren.net, ietf-822@list.cren.net
Subject: Re: Restricting the list
X-Listprocessor-Version: 8.0(dev) -- ListProcessor by CREN

>   I'm going to take the immediate steps of removing this list from its
> globally published status, which may or may not help.

Can't hurt.  Might help.

>   I'm also considering making restricting posting to the subscribers to the
> list, which is more restrictive than the normal situation for ietf lists,
> so I'd like to get your reactions to that before I do so.  I propose that
> such a restriction is not overly troublesome because (1) anyone can still
> subscribe if posting is that important) and (2) postings are really
> meaningful only from people that are fimiliar to the list.

I don't think that's a good idea for reasons already mentioned.

>   Finally, I must note that if such postings continue, CREN will probably
> have to ask for some other site to host the lists, because of the legal
> liabilities involved.
>   What's your pleasure?

Once we have our new LISTSERV system in production, I'll be willing to
host more IETF lists.  It will be a few more weeks though.