Re: NIR list is broadcasting "subscribe" messages.

Fred Swartz <fred.swartz@umich.edu> Wed, 10 March 1993 01:34 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17729; 9 Mar 93 20:34 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa17725; 9 Mar 93 20:34 EST
Received: from kona.CC.McGill.CA by CNRI.Reston.VA.US id aa27884; 9 Mar 93 20:34 EST
Received: by kona.cc.mcgill.ca (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA08151 on Tue, 9 Mar 93 19:11:39 -0500
Received: from merit.edu by kona.cc.mcgill.ca with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA08147 (mail destined for /usr/lib/sendmail -odq -oi -fnir-request nir-out) on Tue, 9 Mar 93 19:11:37 -0500
Return-Path: <swartz@merit.edu>
Received: by merit.edu (5.65/1123-1.0) id AA08460; Tue, 9 Mar 93 19:11:25 -0500
Message-Id: <9303100011.AA08460@merit.edu>
To: raisch@ora.com
Cc: nir@cc.mcgill.ca
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Fred Swartz <fred.swartz@umich.edu>
Subject: Re: NIR list is broadcasting "subscribe" messages.
In-Reply-To: Your message of "Tue, 09 Mar 93 15:46:34 EST." <9303091546.ZM7660@ruby.ora.com>
Date: Tue, 09 Mar 93 19:11:25 -0500
X-Orig-Sender: swartz@merit.edu

>Ummmm... Jill, by redefining a network standard mechanism like
>"mailinglist-request" pointing to the mechanism which subscribes
>one to a mail list, you fly in the face of network convention, and
>are generating a lot of unnecessary confusion in an arena fraught
>with confusion to begin with.

On the contrary, the "mailinglist-request@host" form is quite common,
and I belong to several lists that are run that way, as well as many
that are not.  It's a mess everyone would like solved, though the
path to salvation is unclear.

  -- Fred (fred.swartz@merit.edu)