IETF Logo Mail Archive

Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction

Nat Ballou <NatBa@microsoft.com> Fri, 20 December 1996 19:48 UTC

Received: from cnri by ietf.org id aa21980; 20 Dec 96 14:48 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa18472; 20 Dec 96 14:48 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id NAA20497 for ietf-nntp-outgoing; Fri, 20 Dec 1996 13:45:38 -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 NAA20492 for <ietf-nntp@ACADEM2.ACADEM.COM>; Fri, 20 Dec 1996 13:45:36 -0600 (CST)
Received: from tide03.microsoft.com (firewall-user@tide03.microsoft.com [131.107.3.13]) by academ.com (8.8.3/8.7.1) with ESMTP id NAA06506 for <ietf-nntp@academ.com>; Fri, 20 Dec 1996 13:45:34 -0600 (CST)
Received: by tide03.microsoft.com; id LAA27720; Fri, 20 Dec 1996 11:45:30 -0800 (PST)
Received: from unknown(157.54.17.74) by tide03.microsoft.com via smap (V3.1) id xma027718; Fri, 20 Dec 96 11:45:19 -0800
Received: from IMSMAIL ([157.55.65.201]) by imail2.microsoft.com (8.7.3/8.7.1) with ESMTP id LAA28445 for <ietf-nntp@academ.com>; Fri, 20 Dec 1996 11:45:35 -0800 (PST)
Received: from natba1 - 172.31.178.33 by ims.microsoft.com with Microsoft SMTPSVC; Fri, 20 Dec 1996 11:49:57 -0800
From: Nat Ballou <NatBa@microsoft.com>
To: ietf-nntp@academ.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
Date: Fri, 20 Dec 1996 11:46:17 -0800
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1160
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <04bb357491914c6IMSMAIL@ims.microsoft.com>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> From: Chris Lewis <clewis@nortel.ca>
> To: rsalz@osf.org
> Cc: ietf-nntp@academ.com
> Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
> Date: Thursday, December 19, 1996 9:00 AM
> 
> [...]
>
> 	In the real world even the best possible value isn't always a
> 	usable email address.  The intent here is that the Sender:
> 	should be a valid email address for the originator if available.
> 	In most cases, a full authentication mechanism (such as via
> 	AUTHINFO GENERIC querying a user database) will often be able to
> 	construct a usable email address.

What exactly do you mean by 'usable'?  If you only mean correct syntax,
then I see no value to this discussion.  If you mean it corresponds
to the mailbox of the person being authenticated, then I would claim
your statement here is false - most authentication schemes do not
have the ability to find the 'right' email domain of the user being
authenticated.

Nat

v2.8.7 | Report a Bug | By Email