Received: from SEARN.SUNET.SE (searn.sunet.se [18.104.22.168]) by miles.greatcircle.com (8.7.4/Miles-951221-1) with SMTP id GAA13644 for <list-managers @
COM>; Wed, 22 May 1996 06:49:31 -0700 (PDT)
Message-Id: <199605221349 .
Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R3)
with BSMTP id 4530; Wed, 22 May 96 15:46:48 +0200
Received: from SEARN.SUNET.SE (NJE origin ERIC @
SEARN) by SEARN.SUNET.SE (LMail V1.2b/1.8b) with RFC822 id 2412; Wed, 22 May 1996 15:46:48 +0200
Date: Wed, 22 May 1996 15:40:40 +0200
From: Eric Thomas <ERIC @
Subject: Re: Standard sign-on, sign-of, etc.
To: list-managers @
In-Reply-To: Message of Wed, 22 May 1996 09:21:38 -0400 (EDT) from
This has already been discussed and re-discussed and re-re-discussed. The
bottom line is that in 4 weeks it will have been 10 years that the
syntaxes of SUBSCRIBE and SIGNOFF were established, this is the syntax
users are used to and read about in Internet books, most packages support
it, and packages that don't can be trivially modified to support it. The
main issue is where you send the command, and this is where the flaming
just goes on and on. LISTSERV supports listname-server as a product
independent method to refer to the MLM in charge of the list in question
(which is also useful when you run multiple MLMs on the same machine).
Others have proposed 'listmaster' and yet others have pointed out that
this is usually the address of the human who manages the list. To a large
extent, this is something for the authors of the main packages to decide,
and/or for their respective constituencies to lobby for. This isn't
something for an ad hoc group to attempt to regulate.