Sender header (was Re: ietf-nntp BCP ...)

Chris Newman <Chris.Newman@innosoft.com> Thu, 19 December 1996 00:10 UTC

Received: from cnri by ietf.org id aa13558; 18 Dec 96 19:10 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa28438; 18 Dec 96 19:10 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id SAA11111 for ietf-nntp-outgoing; Wed, 18 Dec 1996 18:08:16 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id SAA11106 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 18:08:13 -0600 (CST)
Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by academ.com (8.8.3/8.7.1) with ESMTP id SAA05568 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 18:08:12 -0600 (CST)
Received: from eleanor.innosoft.com by INNOSOFT.COM (PMDF V5.0-8 #8694) id <01ID5THBLC7GA8CSPC@INNOSOFT.COM> for ietf-nntp@academ.com; Wed, 18 Dec 1996 16:07:18 -0800 (PST)
Date: Wed, 18 Dec 1996 16:08:05 -0800 (PST)
From: Chris Newman <Chris.Newman@innosoft.com>
Subject: Sender header (was Re: ietf-nntp BCP ...)
In-reply-to: <029b347432112c6IMSMAIL@ims.microsoft.com>
To: ietf-nntp@academ.com
Message-id: <Pine.SOL.3.95.961218155928.14276N-100000@eleanor.innosoft.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Wed, 18 Dec 1996, Nat Ballou wrote:
> I believe all we are talking about here is describing how the
> sender: line works today for a current practices doc.  Granted,
> there are cases where even today, it is not of much use.
> 
> However, I believe everyone agrees that the Sender: line (as defined 
> above) does NOT belong in any RFC since not every authentication 
> provider is able to derive an email name for an authenticated user.

Resolving the problems with the Sender header has been addressed in
the DRUMS working group.  There was rough concensus at the San Jose
meeting that the "Sender" header refers to a deliverable mailbox.  So
constructing it from NNTP authentication info may be impossible.

I'm working on an independant header proposal to address the trace
information issue.  It should be coming out as an internet draft in the
next couple days, probably with my suggested filename:
"draft-newman-msgheader-originfo-00.txt".