Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id VAA18392; Tue, 3 Oct 1995 21:58:59 -0400 Received: from wilma.cs.utk.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id VAA18379; Tue, 3 Oct 1995 21:58:54 -0400 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id VAA26592; Tue, 3 Oct 1995 21:58:50 -0400 Message-Id: <199510040158.VAA26592@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: drums@CS.UTK.EDU cc: moore@CS.UTK.EDU Subject: Re: What's the Sender header for? In-reply-to: Your message of "Tue, 03 Oct 1995 20:31:09 CDT." <9510040131.AA13308@dogie.macc.wisc.edu> Date: Tue, 03 Oct 1995 21:58:43 -0400 Sender: moore@CS.UTK.EDU > > I personally feel that Sender should identify the original human > > sender, and that mailing lists shouldn't change it. For them to > > do so removes the ability of a list recipient to see who actually > > sent the message. > > In almost all cases, the original human sender is identified by the > From: header. In all cases, this MUST identify who authored the > message. Is that what you mean by the verb "send"? The person (or people) who authored the message is not necessarily the same as the one person who sent it. I like to point to section A.2 of RFC 822 as examples of the intended use of Sender. It's true that in almost all cases, one person authors a message and that same person sends it. The Sender header is only useful when this is not the case. Keith