Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA19020; Mon, 11 Dec 1995 13:42:20 -0500 Received: by cs.cs.utk.edu (bulk_mailer v1.3); Mon, 11 Dec 1995 13:41:50 -0500 Received: from Tomobiki-Cho.CAC.Washington.EDU by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id NAA18987; Mon, 11 Dec 1995 13:41:43 -0500 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA12381; Mon, 11 Dec 95 10:41:17 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02478; Mon, 11 Dec 95 10:41:07 -0800 Date: Mon, 11 Dec 1995 10:37:53 -0800 (PST) From: Mark Crispin Sender: Mark Crispin Subject: Re: Clarify amibuities) To: Jim Conklin Cc: John Noerenberg , ietf-drums In-Reply-To: <199512111628.LAA16153@info.cren.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 11 Dec 1995 11:32:42 +0100, Jim Conklin wrote: > I agree that little real harm would come from deprecating > Sender. Disagree. It'll force us to start using X-Sender: again. > I think my personal preference would be to clarify that it's only > for human use, as distinguished from use by a mail agent Agree. The only thing that a mail agent should do with Sender: is present it to the human user. I suggest providing a new header for a mailing list which wishes to inject its own name into the headers, e.g. Distributed-From: