Re: Restricting the list

Nathaniel Borenstein <nsb@nsb.fv.com> Tue, 06 February 1996 12:01 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10496; 6 Feb 96 7:01 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10492; 6 Feb 96 7:01 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa05009; 6 Feb 96 7:01 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id GAA06944; Tue, 6 Feb 1996 06:56:21 -0500
Received: from zloty.fv.com (zloty.fv.com [204.250.90.12]) by list.cren.net (8.6.12/8.6.12) with ESMTP id GAA06912; Tue, 6 Feb 1996 06:55:48 -0500
Received: from nsb.fv.com (nsb.fv.com [152.160.80.42]) by zloty.fv.com (8.7.3/8.7.3) with SMTP id DAA29184; Tue, 6 Feb 1996 03:54:30 -0800 (PST)
Received: by nsb.fv.com (4.1/SMI-4.1) id AA07612; Tue, 6 Feb 96 06:54:41 EST
Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.nsb.fv.com.sun4.41 via MS.5.6.nsb.fv.com.sun4_41; Tue, 6 Feb 1996 06:54:40 -0500 (EST)
Message-Id: <Ul5o60CMc50e4NGWZv@nsb.fv.com>
Date: Tue, 6 Feb 1996 06:54:40 -0500 (EST)
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Jim Conklin <conklin@info.cren.net>, ietf-smtp@list.cren.net, ietf-822@list.cren.net, "John W. Noerenberg" <jwn2@qualcomm.com>
Subject: Re: Restricting the list
In-Reply-To: <v03004a00ad3c858b7d47@[129.46.54.71]>
References: <v03004a00ad3c858b7d47@[129.46.54.71]>
X-Listprocessor-Version: 8.0(dev) -- ListProcessor by CREN

Kudos to John Noerenberg for this extremely clear statement:

> I wish it no more than I seek ads for magazine subscriptions I have no
> interest in.  Nevertheless, I'm not about ask the US postmaster to validate
> everyone who might send a message to my postal box.  There is no reason to
> think my email address should be treated any differently.

There is a middle ground worth considering, however.  FV has faced a
similar problem on our "fv-users" list.  We wanted this list to be
available for free & open discussion.  Moderating it would make it look
like we were censoring anti-FV comments, which we certainly weren't. 
Restricting access to FV customers was useless, because some of our
customers are the  very people who would post inappropriate
announcements.  So we evolved another solution:  a bozo list.  The list
operates freely, except that anyone who has developed a history of abuse
is added to a bozo list, and posts from THAT person are re-routed to the
list owner, who can post them or not.

The combination of a strong presence by the list owner, the THREAT of
bozo status, clear explanations of what is and is not appropriate, and
occasional USE of the bozo mechanism can go a long way towards solving
problems like this one.  -- NB
--------
Nathaniel Borenstein <nsb@fv.com>
Chief Scientist, First Virtual Holdings
FAQ & PGP key: nsb+faq@nsb.fv.com