Re: PS -- Re: Restricting the list
Tim Kehres <kehres@ima.com> Wed, 07 February 1996 16:32 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14429;
7 Feb 96 11:32 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14425;
7 Feb 96 11:32 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa08824;
7 Feb 96 11:32 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id LAA04094; Wed, 7 Feb 1996 11:31:08 -0500
Received: from mail.ima.net (root@mail.ima.net [202.75.0.49]) by list.cren.net
(8.6.12/8.6.12) with ESMTP id LAA03989; Wed, 7 Feb 1996 11:30:32 -0500
Received: from ima.com by mail.ima.net (8.6.12/1.14.5) with ESMTP
id AAA11255; Thu, 8 Feb 1996 00:00:41 +0800
Received: by ima.com (8.6.11/1.14.5)
id AAA18157; Thu, 8 Feb 1996 00:13:21 +0800
Message-Id: <Pine.LNX.3.91.960208000427.13240D-100000@ima.com>
Date: Thu, 8 Feb 1996 00:13:21 +0800 (HKT)
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Kehres <kehres@ima.com>
To: Dave Crocker <dcrocker@brandenburg.com>
Cc: Ned Freed <NED@innosoft.com>, ietf-smtp@list.cren.net,
ietf-822@list.cren.net
Subject: Re: PS -- Re: Restricting the list
In-Reply-To: <v03004a06ad3e76a1dc8c@[205.214.160.51]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN
On Wed, 7 Feb 1996, Dave Crocker wrote: > 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? I personally think that this is most practical solution to the problem, however not without it's drawbacks. Many years back I managed a few Internet distribution lists along with the USENET gateways for them. We decided at the time for no moderation on the Internet side, while maintaining full moderation on the USENET side (for many of the same reasons that we are having this discussion today). As many current lists are both gatewayed to environments like USENET as well as feeding downstream distribution lists, the above solution will have the effect of directing potentially a significant amount of traffic the direction of the moderator. As most list moderators do so out of the kindness of their hearts (in other words on their own time as opposed to being part of their job function), the probability of noticable delays in the propogation of the message through the moderator are high. Depending upon the people involved, this may or may not have a significant effect on the usefulness of the list. As long as this characteristic is understood and accepted (as well as being able to identify a willing moderator), I believe that this is the best solution that we currently have available. Best Regards, Tim Kehres International Messaging Associates Ltd
- 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