RFC 822:STANDARD FOR THE FORMAT OF ARPA INTERNET ...
RFC-Ref

host


Click on the red underlined text to get to the source

... differ from the one specified in this standard. This specifica- tion is intended strictly as a definition of what message content format is to be passed BETWEEN hosts. ...


... effect of ASCII HT (horizontal-tab) characters on the appear- ance of text at another network host; therefore, the use of tabs in message headers, though permitted, is discouraged. ...


... msg-id] ["for" addr-spec] ";" date-time ; one per relay, sending host, receiving host, physical ...
... date-time ; one per relay, sending host, receiving host, physical path, link/mail protocol, receiver ...
... The names of the sending and receiving hosts and time-of- receipt may be specified. The "via" parameter may be used, to indicate what physical ...
... queue mail; the internal message iden- tifier that is assigned to the message may be noted, using the "id" parameter. When the sending host uses a destination address specification that the receiving host ...
... host uses a destination address specification that the receiving host reinterprets, by expansion or transformation, the receiving host ...
... host reinterprets, by expansion or transformation, the receiving host may wish to record the original specification, using the "for" parameter. For example, when a copy of mail is sent to the member of a ...
... The uniqueness of the message identifier is guaranteed by the host which generates it. This identifier is intended to be machine readable and not necessarily meaningful to humans. A ...


... user@host.network ...
... Once the network is accessed, it is expected that a message will go directly to the host and that the host will resolve the user name ...
... network is accessed, it is expected that a message will go directly to the host and that the host will resolve the user name, placing the message in the user's mailbox ...
... registry, network, or host. It is a symbolic reference, within a name sub- domain. At times, it is necessary to bypass ...
... bypass standard mechan- isms for resolving such references, using more primitive information, such as a network host address rather than its associated host name ...
... network host address rather than its associated host name. ...
... The local-part of an addr-spec in a mailbox specification (i.e., the host's name for the mailbox) is understood to be whatever the receiving ...
... route> portion of a route-addr is provided for such occa- sions. It specifies the sequence of hosts and/or transmission services that are to be traversed. Both domain ...


... These two "Alfred Neuman" examples have identical seman- tics, as far as the operation of the local host's mail sending (distribution) program (also sometimes called its "mailer") and the remote host ...
... host's mail sending (distribution) program (also sometimes called its "mailer") and the remote host's mail protocol server are concerned. In the first example, the "Alfred Neuman" is ignored by the ...
... single mailbox is shared by several users. The quoted string is ignored by the originating host's mailer, because "Shared@Group.Arpanet" completely specifies the destination ...
... George Jones logs into his host as "Jones". He sends mail himself. ...
... George Jones logs in as Jones on his host. His secre- tary, who logs in as Secy sends mail for him. Replies to the mail should go to George. ...
... From: George Jones <Jones@Host.Net> Sender: Jones@Host ...
... Host.Net> Sender: Jones@Host Reply-To: The Committee ...
... Reply-To: The Committee: Jones@Host.Net, Smith@Other.Org, Doe@Somewhere-Else; ...
... George Jones asks his secretary (Secy@Host) to send a message for him in his capacity as Group. He wants his secre- ...
... From: George Jones <Group@Host> Sender: Secy@Host ...
... Host> Sender: Secy@Host Reply-To: Secy@Host ...
... Host Reply-To: Secy@Host ...
... From: Jones@Host, Smith@Other-Host, ...
... From: Jones@Host, Smith@Other-Host, Doe@Somewhere-Else Sender ...
... Date: 26 Aug 76 1430 EDT From: George Jones<Group@Host> Sender: Secy@SHOST ...
... Sender: Secy@SHOST To: "Al Neuman"@Mad-Host, Sam.Irving@Other-Host ...
... To: "Al Neuman"@Mad-Host, Sam.Irving@Other-Host Message-ID: <some.string@SHOST> ...
... Date : 27 Aug 76 0932 PDT From : Ken Davis <KDavis@This-Host.This-net> Subject : Re: The Syntax in the RFC ...
... Subject : Re: The Syntax in the RFC Sender : KSecy@Other-Host Reply-To : Sam.Irving@Reg.Organization ...
... Tree.Root>, "Sam Irving"@Other-Host;, Standard Distribution: /main/davis/people/standard@Other-Host ...
... Host;, Standard Distribution: /main/davis/people/standard@Other-Host, "<Jones>standard.dist.3"@Tops-20-Host>; ...
... /main/davis/people/standard@Other-Host, "<Jones>standard.dist.3"@Tops-20-Host>; Comment : Sam is away on business. He asked me to handle his mail for him. He'll be able to provide a ...
... preempted Message-ID: <4231.629.XYzi-What@Other-Host> ...


... msg-id] ["for" addr-spec] ";" date-time ; one per relay, sending host, receiving host, physical ...
... date-time ; one per relay, sending host, receiving host, physical path, link/mail protocol, receiver ...



Google
Web
RFC-Ref