Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id XAA00466; Thu, 14 Sep 1995 23:59:18 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 14 Sep 1995 23:59:17 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from wilma.cs.utk.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id XAA00460; Thu, 14 Sep 1995 23:59:16 -0400 Received: from localhost by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id XAA22322; Thu, 14 Sep 1995 23:59:15 -0400 Message-Id: <199509150359.XAA22322@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: Mark Crispin cc: Robert Elz , drums@CS.UTK.EDU, moore@CS.UTK.EDU Subject: Re: summing up: the meaning of the reply-to header In-reply-to: Your message of "Thu, 14 Sep 1995 20:07:46 PDT." Date: Thu, 14 Sep 1995 23:59:08 -0400 Sender: moore@CS.UTK.EDU As for the use of Reply-to to indicate the sender's "real" reply address: I'd treat this similar to the use of Reply-to by mailing lists. It's sanctioned by RFC 822, and outlawing it would cause undue harm, because many user agents don't allow a user to set the From header. So we can't get rid of it, but we can suggest that the From header is a better way to indicate the author's "real" mailing address, and perhaps that user agents MAY (or SHOULD) provide a way to let the author set the From header address. Keith