Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Get The TCP/IP Guide for your own computer.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  TCP/IP Key Applications and Application Protocols
           9  TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
                9  Usenet (Network News) and the TCP/IP Network News Transfer Protocol (NNTP)
                     9  Usenet Overview, Concepts and General Operation

Previous Topic/Section
Usenet Addressing: Newsgroups, Newsgroup Hierarchies and Types
Previous Page
Pages in Current Topic/Section
1
23
Next Page
TCP/IP Network News Transfer Protocol (NNTP)
Next Topic/Section

Usenet Message Format and Special Headers
(Page 1 of 3)

Usenet is designed to permit users to exchange information in the form of messages that are sent from one computer to another. Like any message-based networking application, it is necessary that all Usenet client and server software agree to use a common message format. This ensures that all devices and programs are able to interpret all Usenet articles in a consistent manner.

General Message Format

While Usenet was created as an alternative to e-mail, and there are obviously differences in how each treats messages, there are also many similarities. Both are text-oriented messaging systems with similar needs for communicating both content and control information. The creators of Usenet realized that there would be many advantages to basing the Usenet message format on the one used for e-mail, rather than creating a new format from scratch. For one thing, the e-mail message format was already widely used, and adopting it for Usenet would save implementation time and effort. It would also enhance compatibility between e-mail and Usenet messages, allowing software designed to process or display e-mail to also work with Usenet articles.

For this reason, the Usenet message format was defined based on the RFC 822 standard for e-mail messages, discussed thoroughly in its own subsection of the section on e-mail in this Guide. RFC 822 messages begin with a set of headers that contain control and descriptive information about the message, followed by a blank line and then the message body, which contains the actual content.

One important attribute of the RFC 822 standard is the ability to define custom headers that add to the regular set of headers defined in the standard itself. Usenet articles require some types of information not needed by e-mail, and these can be included in specially-defined headers while still adhering to the basic RFC 822 format. At the same time, headers specific to e-mail that are not needed for Usenet can be omitted.

Thus, there is no structural difference at all between a Usenet article and an e-mail message; they differ only in the kinds of headers they contain, and the values for those headers. For example, a Usenet message will always contain a header specifying the newsgroup(s) to which the article is being posted, but will not carry a “To:” line as an e-mail message would.

Key Concept: Usenet articles use the same RFC 822 message format as electronic mail messages. The only difference between a Usenet article and e-mail message is in the header types and values used in each.



Previous Topic/Section
Usenet Addressing: Newsgroups, Newsgroup Hierarchies and Types
Previous Page
Pages in Current Topic/Section
1
23
Next Page
TCP/IP Network News Transfer Protocol (NNTP)
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.