Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA19171; Tue, 10 Oct 1995 12:31:25 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.3); Tue, 10 Oct 1995 12:31:00 -0400 Received: from Tomobiki-Cho.CAC.Washington.EDU by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id MAA19081; Tue, 10 Oct 1995 12:30:51 -0400 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA07324; Tue, 10 Oct 95 09:30:14 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA07922; Tue, 10 Oct 95 09:29:58 -0700 Date: Tue, 10 Oct 1995 09:26:12 -0700 (PDT) From: Mark Crispin Sender: Mark Crispin Subject: Re: What's the Sender header for? To: Harald.T.Alvestrand@uninett.no Cc: Eric Thomas , Keith Moore , drums@cs.utk.edu In-Reply-To: <199510092058.VAA12428@dale.uninett.no> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 09 Oct 1995 21:58:25 +0100, Harald.T.Alvestrand@uninett.no wrote: > I'm willing to grant Eric's point on Sender: and change the meaning to > be "the entity that last caused the message to be injected into the > mail system". I'm not, because I don't think this is right. This forces resenders to go into a header and remove the Sender: header. Eric also has the habit of sending replies to both the From: and Sender: headers of my messages. That doesn't mean that this practice is correct. > Out of 73 messages from various IETF lists, 62 of them had Sender: fields, > 9 of these were *not* some alias for the list maintainer, and *all* of > these were messages on (SURPRISE.....) the DRUMS list. I don't think this is a valid sample.