Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id EAA03499; Tue, 10 Oct 1995 04:02:07 -0400 Received: by CS.UTK.EDU (bulk_mailer v1.3); Tue, 10 Oct 1995 04:00:28 -0400 Received: from domen.uninett.no by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id EAA03213; Tue, 10 Oct 1995 04:00:23 -0400 Received: from dale.uninett.no by domen.uninett.no with SMTP (PP) id <19801-0@domen.uninett.no>; Tue, 10 Oct 1995 08:59:18 +0100 Received: from dale.uninett.no (localhost [127.0.0.1]) by dale.uninett.no (8.6.9/8.6.9) with ESMTP id VAA12428; Mon, 9 Oct 1995 21:58:27 +0100 Message-Id: <199510092058.VAA12428@dale.uninett.no> From: Harald.T.Alvestrand@uninett.no To: Eric Thomas cc: Keith Moore , drums@cs.utk.edu Subject: Re: What's the Sender header for? In-reply-to: Your message of "Wed, 04 Oct 1995 02:21:24 +0100." <199510040141.VAA17522@CS.UTK.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12425.813272305.1@dale.uninett.no> Date: Mon, 09 Oct 1995 21:58:25 +0100 Sender: hta@dale.uninett.no 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". 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 hope I know when to bow out....... Harald A