IETF Logo Mail Archive

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

Ian King <iking@microsoft.com> Wed, 18 December 1996 22:14 UTC

Received: from cnri by ietf.org id aa10615; 18 Dec 96 17:14 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa26102; 18 Dec 96 17:14 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id QAA10802 for ietf-nntp-outgoing; Wed, 18 Dec 1996 16:12:06 -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 QAA10797 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 16:11:59 -0600 (CST)
Received: from INET-03-IMC.itg.microsoft.com (mail3.microsoft.com [131.107.3.23]) by academ.com (8.8.3/8.7.1) with SMTP id QAA05057 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 16:11:58 -0600 (CST)
Received: by INET-03-IMC.itg.microsoft.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63) id <01BBECEC.D872F4B0@INET-03-IMC.itg.microsoft.com>; Wed, 18 Dec 1996 14:07:47 -0800
Message-ID: <c=US%a=_%p=msft%l=RED-10-MSG-961218220534Z-34325@INET-03-IMC.itg.microsoft.com>
From: Ian King <iking@microsoft.com>
To: 'Rich Salz' <rsalz@osf.org>, "'clewis@nortel.ca'" <clewis@nortel.ca>, "'ietf-nntp@academ.com'" <ietf-nntp@academ.com>
Subject: RE: ietf-nntp BCP for RFC977 server/RFC1036 interaction
Date: Wed, 18 Dec 1996 14:05:34 -0800
X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63
Encoding: 21 TEXT
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Comment embedded below:

>-----Original Message-----
>From:	Rich Salz [SMTP:rsalz@osf.org]
>Sent:	Wednesday, December 18, 1996 11:20 AM
>To:	clewis@nortel.ca; ietf-nntp@academ.com
>Subject:	Re:  ietf-nntp BCP for RFC977 server/RFC1036 interaction
>
>[snip] 
>
>>2) During POST: discard any pre-existing Path:.
>
>No.  Useful for mail/news gateways and to allow clients to reroute
>avoiding "hostile" hosts (r.h.f and Waterloo)
>
>I could not agree more.  Even if someone has maliciously modified the Path
>header, you can trace back to the last 'reputable' host to handle this
>article.  In a past incarnation as a site admin, I got some nasty folks'
>accounts closed this way.    
>
>	/r$

v2.8.7 | Report a Bug | By Email