Re: PS -- Re: Restricting the list
Dave Crocker <dcrocker@brandenburg.com> Wed, 07 February 1996 15:41 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13346;
7 Feb 96 10:41 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13342;
7 Feb 96 10:41 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa07936;
7 Feb 96 10:41 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id KAA01688; Wed, 7 Feb 1996 10:40:44 -0500
Received: from ng.netgate.net (root@ng.netgate.net [204.145.147.10]) by
list.cren.net (8.6.12/8.6.12) with ESMTP id KAA01656;
Wed, 7 Feb 1996 10:40:31 -0500
Received: from [205.214.160.59] (d27.netgate.net [205.214.160.59]) by
ng.netgate.net (8.6.12/8.6.9) with ESMTP id HAA20903;
Wed, 7 Feb 1996 07:46:35 -0800
Message-Id: <v03004a06ad3e76a1dc8c@[205.214.160.51]>
Date: Wed, 7 Feb 1996 07:40:22 -0800
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dave Crocker <dcrocker@brandenburg.com>
To: Ned Freed <NED@innosoft.com>
Cc: ietf-smtp@list.cren.net, ietf-822@list.cren.net
Subject: Re: PS -- Re: Restricting the list
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Sender: dcrocker@ng.netgate.net
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN
At 8:58 AM 2/6/96, Ned Freed wrote: >1. I've already pointed out that filtering on specific origin addresses is > totally ineffective. Ned, What about the following set of mechanisms, each of which I believe I've seen in operation. In combination, they would seem to create a rather powerful filter and control mechanism, I would think. 1. To subscribe to a list, the user sends a request. The list server sends back a verification request. The subscriber returns a confirmation. This provides reasonable assurance that the registered email address is valid. 2. Those who are registered can send messages freely. Those who are not have their messages channeled to the list moderate who decides whether to forward the message or not. One could elaborate this, further, by having non-registered email ALSO get a verification request from the server before sending it on to the moderator. This would filter deprivation of service attacks, I suppose. Thoughts? d/ -------------------- Dave Crocker +1 408 246 8253 Brandenburg Consulting fax: +1 408 249 6205 675 Spruce Dr. dcrocker@brandenburg.com Sunnyvale CA 94086 USA http://www.brandenburg.com Internet Mail Consortium http://www.imc.org, info@imc.org
- Re: PS -- Re: Restricting the list Dave Crocker
- Re: PS -- Re: Restricting the list Tim Kehres
- Re: PS -- Re: Restricting the list Ned Freed
- Re: PS -- Re: Restricting the list John W. Noerenberg
- Re: PS -- Re: Restricting the list Dave Crocker
- Re: PS -- Re: Restricting the list John W. Noerenberg
- Re: PS -- Re: Restricting the list Robert Moskowitz
- Re: PS -- Re: Restricting the list Robert Moskowitz
- Re: PS -- Re: Restricting the list Dave Crocker
- Re: PS -- Re: Restricting the list Ned Freed