🚀 go-pugleaf

kadie@eff.org (Carl M. Kadie) writes:
>Wes Morgan writes:
>
>>>}Section 3: Electronic Mail Policy
>>>}3.4   All mailing lists with more than 10 members must be registered with
>>>}      the ECC staff. [Paragraph 1.21u, CSC]
>
>These lists are already prohibited because they are illegal. Do you
>really want to take even partial responsibility for the lists that you
>do approve of? What if you give it an official University OK, and
>*then* it starts being used for credit cards?

Hmmmm......you may have a point.

>
>I'm enclosing a reference.
>
>If, however, administrators exercise
>the power of prior review, then the court will also hold them and
>their schools liable for the contents of such publications.

Well, I wouldn't be exercising "prior review".  Here's how it would
work (I've already tested this method -- it works):

	1) User asks for mailing list.

	2) I set up a pointer to an address file, WHICH IS OWNED AND
           MAINTAINED by the user.  The user is also designated as the
	   owner of the list, using the standard "maillist-owner" and 
	   "maillist-request" aliases.  If user "jbuser01" comes to me
	   and asks me to set up a mailing list named "snarf", here's
	   all I have to do (sendmail admins take note):

		In the master alias file (mine is /usr/lib/aliases):

		snarf: :include:/usr4/students/jbuser01/snarflist
		snarf-request: jbuser01
		snarf-owner: jbuser01

	   Whenever a piece of mail comes in for "snarf@engr.uky.edu",
	   the mail system consults the file "snarflist" in jbuser01's
	   directory; he owns the file, and I'm out of the loop.

	3) The user runs the list, adding and deleting members and
	   handling the distribution.

The sum total of my participation is the addition of the necessary lines
in the master alias file.  I wouldn't have any input at all to the contents
of the list.

To me, this is similar to starting a college newspaper.  I give them office
space and a means of delivery; the rest of it is theirs.  Would this consti-
tute "prior review"?  What if I eliminate the involvement of the University
Counsel and just create any mailing list upon request, using this system?
Would that eliminate any potential liability?

-- 
 morgan@ms.uky.edu    |Wes Morgan, not speaking for|     ....!ukma!ukecc!morgan
 morgan@engr.uky.edu  |the University of Kentucky's|   morgan%engr.uky.edu@UKCC
 morgan@ie.pa.uky.edu |Engineering Computing Center| morgan@wuarchive.wustl.edu
        "I was going to rip your head off, but I'm past that now."