RFC-1036:[Previous][Up to Table of Contents] [Next]
RFC1036 2.2.13. Xref

This line contains the name of the host (with domains omitted) and a white space separated list of colon-separated pairs of newsgroup names and message numbers. These are the newsgroups listed in the Newsgroups line and the corresponding message numbers from the spool directory.

This is only of value to the local system, so it should not be transmitted. For example, in:

Path: seismo!lll-crg!lll-lcc!pyramid!decwrl!reid

From: reid@decwrl.DEC.COM (Brian Reid)

Newsgroups: news.lists,news.groups

Subject: USENET READERSHIP SUMMARY REPORT FOR SEP 86

Message-ID: <5658@decwrl.DEC.COM>

Date: 1 Oct 86 11:26:15 GMT

Organization: DEC Western Research Laboratory

Lines: 441

Approved: reid@decwrl.UUCP

Xref: seismo news.lists:461 news.groups:6378

the Xref line shows that the message is message number 461 in the newsgroup news.lists, and message number 6378 in the newsgroup news.groups, on host seismo. This information may be used by certain user interfaces.

RFC1036: [Source:"RFC-1036"] [Last Changed:December 1987] [Copyright: 1987 M. Horton, R. Adams]
RFC-1036:[Previous][Up to Table of Contents] [Next]



(Corrections, notes, and links for Usenet RKT.)
by Mib Software, INN customization and consulting

Newsreader software should never generate an XREF header.

-B-r-o-a-d-e-n- your knowledge

Up to RFC1036 2.2. Optional Headers


RKT Rapid-Links:[Search] [RKT Tips] Path:For Developers / NNTProtocol / RFC1036 / Optional Header lines / 0060.htm