?? 00000018.htm
字號:
interprocess communication environment (IPCE). An IPCE may cover one <br /> network, several networks, or a subset of a network. It is important <br /> to realize that transport systems (or IPCEs) are not one-to-one with <br /> networks. A process can communicate directly with another process <br /> through any mutually known IPCE. Mail is an application or use of <br /> interprocess communication. Mail can be communicated between <br /> processes in different IPCEs by relaying through a process connected <br /> to two (or more) IPCEs. More specifically, mail can be relayed <br /> between hosts on different transport systems by a host on both <br /> transport systems. <br />Postel [Page 1] <br /> <br /> <br />August 1982 RFC 821 <br />Simple Mail Transfer Protocol <br />2. THE SMTP MODEL <br /> The SMTP design is based on the following model of communication: as <br /> the result of a user mail request, the sender-SMTP establishes a <br /> two-way transmission channel to a receiver-SMTP. The receiver-SMTP <br /> may be either the ultimate destination or an intermediate. SMTP <br /> commands are generated by the sender-SMTP and sent to the <br /> receiver-SMTP. SMTP replies are sent from the receiver-SMTP to the <br /> sender-SMTP in response to the commands. <br /> Once the transmission channel is established, the SMTP-sender sends a <br /> MAIL command indicating the sender of the mail. If the SMTP-receiver <br /> can accept mail it responds with an OK reply. The SMTP-sender then <br /> sends a RCPT command identifying a recipient of the mail. If the <br /> SMTP-receiver can accept mail for that recipient it responds with an <br /> OK reply; if not, it responds with a reply rejecting that recipient <br /> (but not the whole mail transaction). The SMTP-sender and <br /> SMTP-receiver may negotiate several recipients. When the recipients <br /> have been negotiated the SMTP-sender sends the mail data, terminating <br /> with a special sequence. If the SMTP-receiver successfully processes <br /> the mail data it responds with an OK reply. The dialog is purposely <br /> lock-step, one-at-a-time. <br /> ------------------------------------------------------------- <br /> <br /> +----------+ +----------+ <br /> +------+ | | | | <br /> | User |<-->| | SMTP | | <br /> +------+ | Sender- |Commands/Replies| Receiver-| <br /> +------+ | SMTP |<-------------->| SMTP | +------+ <br /> | File |<-->| | and Mail | |<-->| File | <br /> |System| | | | | |System| <br /> +------+ +----------+ +----------+ +------+ <br /> <br /> Sender-SMTP Receiver-SMTP <br /> Model for SMTP Use <br /> Figure 1 <br /> ------------------------------------------------------------- <br /> The SMTP provides mechanisms for the transmission of mail; directly <br /> from the sending user's host to the receiving user's host when the <br />[Page 2] Postel <br /> <br /> <br />RFC 821 August 1982 <br /> Simple Mail Transfer Protocol <br /> two host are connected to the same transport service, or via one or <br /> more relay SMTP-servers when the source and destination hosts are not <br /> connected to the same transport service. <br /> To be able to provide the relay capability the SMTP-server must be <br /> supplied with the name of the ultimate destination host as well as <br /> the destination mailbox name. <br /> The argument to the MAIL command is a reverse-path, which specifies <br /> who the mail is from. The argument to the RCPT command is a <br /> forward-path, which specifies who the mail is to. The forward-path <br /> is a source route, while the reverse-path is a return route (which <br /> may be used to return a message to the sender when an error occurs <br /> with a relayed message). <br /> When the same message is sent to multiple recipients the SMTP <br /> encourages the transmission of only one copy of the data for all the <br /> recipients at the same destination host. <br /> The mail commands and replies have a rigid syntax. Replies also have <br /> a numeric code. In the following, examples appear which use actual <br /> commands and replies. The complete lists of commands and replies <br /> appears in Section 4 on specifications. <br /> Commands and replies are not case sensitive. That is, a command or <br /> reply word may be upper case, lower case, or any mixture of upper and <br /> lower case. Note that this is not true of mailbox user names. For <br /> some hosts the user name is case sensitive, and SMTP implementations <br /> must take case to preserve the case of user names as they appear in <br /> mailbox arguments. Host names are not case sensitive. <br /> Commands and replies are composed of characters from the ASCII <br /> character set [1]. When the transport service provides an 8-bit byte <br /> (octet) transmission channel, each 7-bit character is transmitted <br /> right justified in an octet with the high order bit cleared to zero. <br /> When specifying the general form of a command or reply, an argument <br /> (or special symbol) will be denoted by a meta-linguistic variable (or <br /> constant), for example, "<string>" or "<reverse-path>". Here the <br />
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -