I thought it would be possible to see what other servers the
newsserver I connect to gets its messages from by looking at the
message Path headers.
However, they are all set to 'not-for-mail'.
Here's the Path: header I see for your post:
Path: usenet.inf.ed.ac.uk!nntp-feed.chiark.greenend.org.uk!ewrotcd!
+ feeds.news.ox.ac.uk!news.ox.ac.uk!2.eu.feeder.erje.net!feeder.erje.net! >+ feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!193.141.40.65.
+ MISMATCH!npeer.as286.net!npeer-ng0.as286.net!peer04.ams1!peer.ams1.
+ xlned.com!news.xlned.com!peer02.ams4!peer.am4.highwinds-media.com!news. >+ highwinds-media.com!fx17.ams4.POSTED!not-for-mail
The server I'm reading it from is usenet.inf.ed.ac.uk. It received
it from nntp-feed.chiark.greenend.org.uk.
I thought it would be possible to see what other servers the
newsserver I connect to gets its messages from by looking at the
message Path headers.
However, they are all set to 'not-for-mail'.
That's not what I think it says in RFC 850. Is that header no longer
used?
Richard
Path: ...!peer.am4.highwinds-media.com!news.highwinds-media.com!fx17.ams4.POSTED!not-for-mail
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
anonymous@example.invalid wrote:
I thought it would be possible to see what other servers the
newsserver I connect to gets its messages from by looking at the
message Path headers.
However, they are all set to 'not-for-mail'.
It looks like you're reading it backwards.
Here's the Path: header I see for your post:
Path: usenet.inf.ed.ac.uk!nntp-feed.chiark.greenend.org.uk!ewrotcd!
+ feeds.news.ox.ac.uk!news.ox.ac.uk!2.eu.feeder.erje.net!feeder.erje.net! >+ feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!193.141.40.65.
+ MISMATCH!npeer.as286.net!npeer-ng0.as286.net!peer04.ams1!peer.ams1.
+ xlned.com!news.xlned.com!peer02.ams4!peer.am4.highwinds-media.com!news. >+ highwinds-media.com!fx17.ams4.POSTED!not-for-mail
The server I'm reading it from is usenet.inf.ed.ac.uk. It received
it from nntp-feed.chiark.greenend.org.uk.
The path has the form of a UUCP mail address, host!host!...!host!user.
In the distant past, the user part would be the actual username of the >poster, and the path could be used to sent a reply. Nowadays servers
insert "not-for-mail" as a placeholder where the username would be.
You are using a Usenet service which resells service from Omicron's
HW Media Usenet backbone.
<https://burwinch.github.io/usenet_tree/usenet_tree.svg>
The HW Media Usenet backbone stopped providing the real 'Path' header
to customers back in 2012. The alleged reason was "to protect our proprietary architecture".
You are using a Usenet service which resells service from Omicron's
HW Media Usenet backbone.
<https://burwinch.github.io/usenet_tree/usenet_tree.svg>
The HW Media Usenet backbone stopped providing the real 'Path' header
to customers back in 2012. The alleged reason was "to protect our >proprietary architecture".
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 78:37:30 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,332,979 |
Posted today: | 1 |