Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id PAA06434; Tue, 10 Oct 1995 15:35:36 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.3); Tue, 10 Oct 1995 15:35:24 -0400 Received: from wilma.cs.utk.edu by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id PAA06391; Tue, 10 Oct 1995 15:35:22 -0400 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id PAA04873; Tue, 10 Oct 1995 15:35:18 -0400 Message-Id: <199510101935.PAA04873@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, 10 Oct 1995 14:14:22 CDT." <9510101914.AA18082@dogie.macc.wisc.edu> Date: Tue, 10 Oct 1995 15:35:12 -0400 Sender: moore@cs.utk.edu > This is related to Keith's report about MH's behavior that the > "real electronic mail address" is included in the message. I am > asking where this concept of "real address" comes from. What makes > an address "real"? Why is it important to distinguish? Isn't > Postmaster@munnari.oz.au just as "real" as any other workable address? Instead of "real", how about "a stable address that uniquely identifies the AGENT who sent the message". And as for "AGENT", I'd define this as: + for any message sent as a result of a specific human action, the AGENT is that human and the Sender address should be a stable address that *uniquely identifies* that human. + for any message sent as a result of an automatic process, the AGENT is the human being responsible for maintaining that process and fixing it if it breaks, and the Sender address should be a stable address such that mail sent to the address will reliably reach that human.