ietf-nntp BCP for RFC977 server/RFC1036 interaction

[Ian King]

Comment embedded below:

>-----Original Message-----
>From:	Rich Salz [SMTP:rsalz at osf.org]
>Sent:	Wednesday, December 18, 1996 11:20 AM
>To:	clewis at nortel.ca; ietf-nntp at 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$