IETF Logo Mail Archive

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

Evan Champion <evanc@synapse.net> Wed, 18 December 1996 23:52 UTC

Received: from cnri by ietf.org id aa13234; 18 Dec 96 18:52 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa28100; 18 Dec 96 18:52 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id RAA11001 for ietf-nntp-outgoing; Wed, 18 Dec 1996 17:50:14 -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 RAA10996 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 17:50:12 -0600 (CST)
Received: from clarinet.synapse.net (clarinet.synapse.net [199.84.54.19]) by academ.com (8.8.3/8.7.1) with ESMTP id RAA05480 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 17:50:08 -0600 (CST)
Received: from piano.synapse.net (piano.synapse.net [199.84.54.20]) by clarinet.synapse.net (8.8.4/8.8.4) with ESMTP id SAA29252; Wed, 18 Dec 1996 18:50:07 -0500 (EST)
Received: from piano.synapse.net (localhost [127.0.0.1]) by piano.synapse.net (8.8.4/8.8.4) with SMTP id SAA05555; Wed, 18 Dec 1996 18:50:06 -0500 (EST)
Date: Wed, 18 Dec 1996 18:50:06 -0500 (EST)
From: Evan Champion <evanc@synapse.net>
To: USENET news manager <newsmaster@ucs.cam.ac.uk>
cc: ietf-nntp@academ.com
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
In-Reply-To: <199612181943.TAA27274@lyra.csx.cam.ac.uk>
Message-ID: <Pine.BSI.3.91.961218184409.951I-100000@piano.synapse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Wed, 18 Dec 1996, USENET news manager wrote:

> That's not what INN does - it rejects POST attempts with the message
> 
> Can't set system "NNTP-Posting-Host" header
> 
> Accepting postings but inserting the correct information seems like a reasonable
> alternative approach.

Circa line 430 in nnrpd.c (1.5.1), NNTP-Posting-Host is always rewritten,
so it would seem that the fix would be to change the FALSE to TRUE in line
66 to allow clients to specify NNTP-Posting-Host and let nnrpd take care 
of it later on as it does today.

Evan
--
Evan Champion            * Director, Network Operations
mailto:evanc@synapse.net * Directeur, Exploitation du reseau
http://www.synapse.net/  * Synapse Internet

v2.8.7 | Report a Bug | By Email