?? 00000017.htm
字號:
<?xml version="1.0" encoding="gb2312"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=gb2312"/><title>POP3 turbolinux </title></head><body><center><h1>BBS 水木清華站∶精華區(qū)</h1></center><a name="top"></a>發(fā)信人: hellow (收復(fù)臺灣是我心), 信區(qū): Embedded <br />標(biāo) 題: POP3 <br />發(fā)信站: BBS 水木清華站 (Sun Nov 5 09:39:33 2000) <br /> <br /> <br />Network Working Group J. Myers <br />Request for Comments: 1939 Carnegie Mellon <br />STD: 53 M. Rose <br />Obsoletes: 1725 Dover Beach Consulting, Inc. <br />Category: Standards Track May 1996 <br /> Post Office Protocol - Version 3 <br />Status of this Memo <br /> This document specifies an Internet standards track protocol for the <br /> Internet community, and requests discussion and suggestions for <br /> improvements. Please refer to the current edition of the "Internet <br /> Official Protocol Standards" (STD 1) for the standardization state <br /> and status of this protocol. Distribution of this memo is unlimited. <br />Table of Contents <br /> 1. Introduction ................................................ 2 <br /> 2. A Short Digression .......................................... 2 <br /> 3. Basic Operation ............................................. 3 <br /> 4. The AUTHORIZATION State ..................................... 4 <br /> QUIT Command ................................................ 5 <br /> 5. The TRANSACTION State ....................................... 5 <br /> STAT Command ................................................ 6 <br /> LIST Command ................................................ 6 <br /> RETR Command ................................................ 8 <br /> DELE Command ................................................ 8 <br /> NOOP Command ................................................ 9 <br /> RSET Command ................................................ 9 <br /> 6. The UPDATE State ............................................ 10 <br /> QUIT Command ................................................ 10 <br /> 7. Optional POP3 Commands ...................................... 11 <br /> TOP Command ................................................. 11 <br /> UIDL Command ................................................ 12 <br /> USER Command ................................................ 13 <br /> PASS Command ................................................ 14 <br /> APOP Command ................................................ 15 <br /> 8. Scaling and Operational Considerations ...................... 16 <br /> 9. POP3 Command Summary ........................................ 18 <br /> 10. Example POP3 Session ....................................... 19 <br /> 11. Message Format ............................................. 19 <br /> 12. References ................................................. 20 <br /> 13. Security Considerations .................................... 20 <br /> 14. Acknowledgements ........................................... 20 <br /> 15. Authors' Addresses ......................................... 21 <br /> Appendix A. Differences from RFC 1725 .......................... 22 <br />Myers & Rose Standards Track [Page 1] <br /> <br />RFC 1939 POP3 May 1996 <br /> Appendix B. Command Index ...................................... 23 <br />1. Introduction <br /> On certain types of smaller nodes in the Internet it is often <br /> impractical to maintain a message transport system (MTS). For <br /> example, a workstation may not have sufficient resources (cycles, <br /> disk space) in order to permit a SMTP server [RFC821] and associated <br /> local mail delivery system to be kept resident and continuously <br /> running. Similarly, it may be expensive (or impossible) to keep a <br /> personal computer interconnected to an IP-style network for long <br /> amounts of time (the node is lacking the resource known as <br /> "connectivity"). <br /> Despite this, it is often very useful to be able to manage mail on <br /> these smaller nodes, and they often support a user agent (UA) to aid <br /> the tasks of mail handling. To solve this problem, a node which can <br /> support an MTS entity offers a maildrop service to these less endowed <br /> nodes. The Post Office Protocol - Version 3 (POP3) is intended to <br /> permit a workstation to dynamically access a maildrop on a server <br /> host in a useful fashion. Usually, this means that the POP3 protocol <br /> is used to allow a workstation to retrieve mail that the server is <br /> holding for it. <br /> POP3 is not intended to provide extensive manipulation operations of <br /> mail on the server; normally, mail is downloaded and then deleted. A <br /> more advanced (and complex) protocol, IMAP4, is discussed in <br /> [RFC1730]. <br /> For the remainder of this memo, the term "client host" refers to a <br /> host making use of the POP3 service, while the term "server host" <br /> refers to a host which offers the POP3 service. <br />2. A Short Digression <br /> This memo does not specify how a client host enters mail into the <br /> transport system, although a method consistent with the philosophy of <br /> this memo is presented here: <br /> When the user agent on a client host wishes to enter a message <br /> into the transport system, it establishes an SMTP connection to <br />
?? 快捷鍵說明
復(fù)制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -