| 
 | 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 KozierokAuthor 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.
 |  |  | 
| 
 
 
 | 
 
 Usenet Message Format and Special Headers
 (Page 3 of 3)
 
 Additional Usenet Headers Usenet messages may also contain 
additional headers, just as is the case with e-mail messages. Some of 
these headers are entirely custom and are included by individual 
users to provide extra information about an article. Others are used 
in many or even most current Usenet articles, and have become almost 
de facto standard headers through common use. Many of these 
custom headers are preceded by X-, indicating that they 
are experimental or extra headers. Some of the more frequently encountered 
additional Usenet headers are shown in Table 265. 
 Table 265: Common Additional Usenet Headers  
| Header 
Name | Description |  
| NNTP-Posting-Host: | Specifies the IP address or the 
DNS domain name of the host used to originally post the message. This 
is usually either the address of the client that the author used for 
posting the message, or the sender's local NNTP server. |  
| User-Agent: (or)X-Newsreader:
 | The name and 
version number of the software used to post the message. |  
| X-Trace: | Provides additional information 
that can be used to trace the message. |  
| X-Complaints-To: | An e-mail address 
to use to report abusive messages. This header is now included automatically 
by many Internet Service Providers. | 
Usenet MIME Messages
 Since Usenet follows the RFC 822 
standard, Multipurpose 
Internet Mail Extensions (MIME) can be 
used to format Usenet messages. When this is done, you will see the 
usual MIME 
headers (such as MIME-Version, 
Content-Type and so forth) in the message.  Note that the use of MIME in Usenet 
messages is somewhat controversial. Some newsreaders are not MIME-compliant 
and make a mess when trying to display some of these messages, and many 
Usenet veterans object to the use of anything but plain text in Usenet 
messages. Despite this, MIME messages are becoming more common, for 
better or worse.   
 
 
 | 
 | 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! |  
|  | 
 | 
 
 
 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.
 |