Xref: utzoo news.software.b:8436 news.software.nntp:1432
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!linac!mp.cs.niu.edu!rickert
From: rickert@mp.cs.niu.edu (Neil Rickert)
Newsgroups: news.software.b,news.software.nntp
Subject: Re: What should go in the Path for nntp postings
Message-ID: <1991Jun26.114451.31400@mp.cs.niu.edu>
Date: 26 Jun 91 11:44:51 GMT
References: <6106@gazette.bcm.tmc.edu> <1991Jun21.162641.900@mp.cs.niu.edu> <1991Jun24.152258.6663@Daisy.EE.UND.AC.ZA>
Organization: Northern Illinois University
Lines: 18

In article <1991Jun24.152258.6663@Daisy.EE.UND.AC.ZA> barrett@Daisy.EE.UND.AC.ZA (Alan P Barrett) writes:
>It seems to me that the correct thing is for the remote site to generate
>an Path line that points to a {bit bucket, auto-replyer, human
>administrator} on the remote site.  The Path line should not include the
>originator's login id or site name.  This seems to satisfy Neil's point
>4 (and if the Path points to a bit bicket then I think that also
>satisfies point 3).

  Perhaps one should go further.  How about the Path: ALWAYS pointing to a
bit bucket, even when posted at a site with full news locally available.
Then we get out of the state where some sites reply to 'From:' and some to
'Path:'.  Is it time to force the issue?

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940