Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id RAA24870; Mon, 18 Dec 1995 17:27:10 -0500
Received: by CS.UTK.EDU (bulk_mailer v1.3); Mon, 18 Dec 1995 17:24:11 -0500
Received: from info.cren.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK)
	id RAA24629; Mon, 18 Dec 1995 17:24:09 -0500
Received: from [192.52.179.12] (conklin-180c.cren.net [192.52.179.12]) by info.cren.net (8.6.12/8.6.4 (CREN)) with SMTP id RAA27410; Mon, 18 Dec 1995 17:18:55 -0500
Message-Id: <199512182218.RAA27410@info.cren.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 18 Dec 1995 17:23:12 +0100
To: Mark Crispin <MRC@Panda.COM>
From: conklin@info.cren.net (Jim Conklin)
Subject: Re: Clarify amibuities)
Cc: John Noerenberg <jwn2@qualcomm.com>, ietf-drums <drums@cs.utk.edu>

At 10:37 AM 12/11/95 -0800, Mark Crispin wrote:
>I suggest providing a new header for a mailing list which wishes to inject its
>own name into the headers, e.g. Distributed-From:

  As long as it's a SHOULD, I think that's a good idea, but I'd like the
name to contain the work "list" explicitly for clarity.  For example,
Distribution-List: or Mailing-List: or List-Sender: or Sender-List: would
all be fine by me.

Jim