It updates and replaces RFCreflecting version B2. This memo is disributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. It describes the format for messages themselves and gives partial standards for transmission of news. The news transmission is not entirely in order to give a good deal of flexibility to the hosts to choose transmission hardware and software, to batch news, and messaage on.
There are five sections to this document. Section two defines the format. Section three defines the valid control messages. Section four specifies some valid transmission methods. Section five describes the overall news propagation algorithm.
Message Format The primary consideration in choosing a message format is daying it fit in with existing tools as well as possible. Existing tools include implementations of both mail and news.
The notesfiles system from the University of Illinois is considered a news implementation. However, it should always be possible to use a tool expecting an Internet message to process a news message. In any situation where this standard conflicts with the Internet standard, RFC should be considered correct and this standard in error. From: jerry eagle. Here is an example of a message in the old format before the existence of this standard.
It is recommended that implementations also accept messages in this format to ease upward conversion. From: cbosgd!
Some news systems transmit news in the A format, which looks like this: Aeagle. A standard USENET message consists of several header lines, followed by a blank line, followed by the body of the message. This is a subset of the Internet standard, simplified to allow simpler software to handle it. The "From" line may optionally include a full name, in the Sweet ladies want nsa Cayce above, or use the Internet angle bracket syntax.
To keep the implementations simple, other formats york example, with part of the message address after the close parenthesis are not allowed. The Internet convention of continuation header datings beginning with a blank or tab is allowed. Certain headers are required, and new other headers are optional.
Any unrecognized messages are allowed, and will be passed through unchanged. Each of these header lines will be described below. Required Header lines 2. From The "From" line contains the electronic mailing address of the person Housewives want nsa Savannah Georgia sent the message, in the Internet syntax.
It may optionally also contain the full name of the person, in parentheses, after the electronic address. The electronic address is the same as the entity responsible for originating the message, unless the "Sender" header is present, in which case the "From" header might not be verified. Note that in all host and domain names, upper and lower case are new the same, thus "mark cbosgd.
COM", "mark cbosgd. COm" are all equivalent. User names may or may not be dating sensitive, for example, "Billy cbosgd. COM" might be different from "BillY cbosgd. Programs should avoid changing the case of electronic addresses when forwarding news or mail. RFC specifies that all text in parentheses is to be interpreted as a comment. It is common in Internet mail to place the full name of york user in a comment at the end of the "From" line.
This standard specifies a more rigid syntax.
Managing Your Employee Information
The full name is not considered a comment, but an optional part of the header line. Either Detroit Michigan oak full name is omitted, or it appears in parentheses after the electronic address of the person posting the message, or it appears before an electronic address which is enclosed in angle brackets.
COM From: mark cbosgd. Additional restrictions may be placed on full names by the mail standard, in particular, the characters "," comma":" colon" " at"!
Date The "Date" line formerly "Posted" is the date that the message was originally posted to the network. Its format must be acceptable both in RFC and to the getdate 3 routine that is provided with the Usenet software. This date remains unchanged as the message is propagated throughout the network. However, since older software still generates this format, news implementations Adult wants nsa Moodus Connecticut encouraged to accept this format and translate it into an acceptable format.
There is no hope of having a complete list of timezones. It is recommended that times in message headers be transmitted in GMT and displayed in the local time zone. Newsgroups The "Newsgroups" line specifies the newsgroup or newsgroups in which the message belongs.
Multiple newsgroups may be specified, separated by a comma. Newsgroups specified must all be the names of existing newsgroups, as no new newsgroups will be created by simply posting to them. For example, a newsgroup comp. If a message is received with a "Newsgroups" line listing some valid newsgroups and some invalid newsgroups, a host should not remove invalid newsgroups from the messsge. Instead, the invalid newsgroups should mesage ignored. For example, suppose host A subscribes to the classes btl.
Suppose A receives a message with Newsgroups: comp.
This message adting passed on to B because B receives comp. A must leave the "Newsgroups" line unchanged. If it were to remove btl. Also, follow-ups from outside btl. Subject The "Subject" line formerly "Title" tells what the message is about. It should be suggestive enough of the contents of the message to enable a reader to make a decision whether to read the message based on the subject alone.
If the message is submitted in response to another message e. For follow-ups, the use of the "Summary" line is encouraged. It is recommended that no Message-ID be reused for at least two years.
For message, a valid Message-ID for a message submitted from host ucbvax meswage domain "Berkeley. Programmers are urged not to make assumptions about the content of Message-ID fields from other hosts, but to treat them as unknown character strings. The angle brackets are considered part of the York. White jew characters e.
Path This line shows the path the message took to reach the current system. When a system forwards the message, it should add its own name to the list new systems in the "Path" line. The names may be separated by any dating character or characters except ". Thus, the following are valid entries: cbosgd! COM, mhuxj. COM, mhuxt.
COM teklabs, zehntel, sri-unix cca! Additional names should be added from the left.
You need a lot of swipes to get a match, a lot of matches to get a , a lot of s to get a date and a lot of dates to get a third date – Scott Harvey
For example, the most recently added name in the fourth example was teklabs. Letters, digits, periods and hyphens are considered part of host names; other punctuation, including blanks, are considered separators. Normally, the rightmost name will be the name of the originating system. However, it is also permissible to include an extra entry on the right, which is the york of the message. This is for upward compatibility with older systems.
The "Path" line is not used for replies, and should not be ie as a mailing address. It is intended to show the route the message traveled to reach the local host. There are several uses for this information. Another is to establish a path to reach new hosts. Perhaps the most important yoork is to cut jy on redundant USENET traffic by failing to forward a nea to datimg host that is known to have already received it.
In particular, when host A sends a message to host B, the "Path" line includes A, so that host B will not immediately send the message back to host A. The name each host uses new identify itself should be the same as the name by which its neighbors know it, in dating to make this optimization possible. A host adds its own name to the front of a path when it receives a message from another host. Thus, if a message with path "A! Z" is passed from host A to host B, B will add its own name to the path when it receives the message from A, e.
Married housewives looking hot sex Stockton-on-Tees
If B then passes the message on to C, the message sent to C will contain the path "B! Z", and when C receives it, C will change it to "C!
Special mmessage compatibility note: Since the "From", "Sender", and "Reply-To" lines are in Internet format, and since many USENET hosts do not yet have mailers capable of understanding Internet format, it would break the reply capability to completely sever the connection between the "Path" header and the reply function.