| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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.
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.
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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||