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

Brian Kantor <brian@nothing.ucsd.edu> Thu, 19 December 1996 04:51 UTC

Received: from cnri by ietf.org id aa23368; 18 Dec 96 23:51 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa00874; 18 Dec 96 23:51 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id WAA12011 for ietf-nntp-outgoing; Wed, 18 Dec 1996 22:47:13 -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 WAA12006 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 22:47:11 -0600 (CST)
Received: from nothing.ucsd.edu (nothing.ucsd.edu [132.239.1.4]) by academ.com (8.8.3/8.7.1) with ESMTP id WAA08930 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 22:47:09 -0600 (CST)
Received: by nothing.ucsd.edu (8.8.3/UCSDGENERIC.5) id EAA22178 to ; Thu, 19 Dec 1996 04:46:00 GMT
Date: Thu, 19 Dec 1996 04:46:00 GMT
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199612190446.EAA22178@nothing.ucsd.edu>
To: evanc@synapse.net, newsmaster@ucs.cam.ac.uk
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
Cc: ietf-nntp@academ.com
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

NNTP-Posting-Host is specifically to be set by the SERVER.  No client
should attempt to set it; whether you flag that as an error or simply
replace it depends on how you feel about people attempting to forge
news into your system.  (That's why I put it into NNTP in the first
place!)  Personally, I find rejecting the posting to be more satisfying.
	- Brian