throbber
Network Working Group
`Request for Comments: 918
`
`J. K. Reynolds
`ISI
`October 1984
`
`POST OFFICE PROTOCOL
`
`Status of this Memo
`
` This RFC suggests a simple method for workstations to dynamically
` access mail from a mailbox server. This RFC specifies a proposed
` protocol for the ARPA-Internet community, and requests discussion and
` suggestions for improvement.
`
`Introduction
`
` The intent of the Post Office Protocol (POP) is to allow a user’s
` workstation to access mail from a mailbox server. It is expected
` that mail will be posted from the workstation to the mailbox server
` via the Simple Mail Transfer Protocol (SMTP). For further
` information see RFC-821 [1] and RFC-822 [2].
`
` The status of this protocol is experimental, and this protocol is
` dependent upon TCP.
`
`The Protocol
`
` The protocol is for the server to be listening for a connection.
` When a connection is opened the server sends a greeting message and
` waits for commands. When commands are received the server acts on
` them and responds with replies.
`
` The client opens a connection, waits for the greeting, then sends the
` USER and then the PASS commands to establish authorization to access
` mailboxes. The client begins a mail reading transaction with either
` an RDEL (to read and delete all messages from a mailbox) or a RETR
` (to simply read all messages from a mailbox). The server opens and
` locks the mailbox, and responds with the number of characters in the
` mailbox. Then the client asks for the data to be sent by issuing the
` RCEV command. The server responds by sending the mail data. When
` all the data has been received the client sends the RCVD command. If
` the transaction started with the RDEL command the server now deletes
` the mail data from the mailbox. In any case, the server closes and
` unlocks the mailbox. The client terminates the session with the QUIT
` command.
`
`Reynolds
`
`[Page 1]
`
`CODE200 ET AL. EXHIBIT 1026
`Page 1 of 5
`
`

`

`
`Post Office Protocol RFC 918
`
` The Normal Scenario
`
` Client Server
` ------ ------
` Wait for Connection
` Open Connection -->
` <-- +OK
` Wait for Command
` USER Fred -->
` <-- +OK
` Wait for Command
` PASS password -->
` <-- +OK
` Wait for Command
` RDEL mailbox --> (open and lock mailbox)
` <-- #xxx
` Wait for Command
` RCEV -->
` <-- (send a copy of mail)
` Wait for Command
` RCVD --> (deletes mail from mailbox, unlock
` and close mailbox)
` <-- +OK
` Wait for Command
` QUIT -->
` <-- +OK
` Close connection --> <-- Close connection
` Wait for Connection (go back to start)
`
`Definitions of Commands and Replies
`
` Summary of Commands and Replies
`
` Commands Replies
` -------- -------
` USER name +OK
` PASS password -Error
` RETR mailbox #xxx
` RDEL mailbox
` RCEV
` RCVD
` QUIT
` NOOP
` RSET
`
`Reynolds [Page 2]
`
`CODE200 ET AL. EXHIBIT 1026
`Page 2 of 5
`
`

`

`
`Post Office Protocol RFC 918
`
` Commands
`
` USER name
`
` This command identifies the user to the server. It must be
` followed by the PASS command.
`
` Possible responses: "+OK" or "-ERR"
`
` PASS password
`
` The PASS command carries the password authenticating this user.
` Together the USER name and PASS password are used by the server
` to control access to the mailboxes.
`
` Possible responses: "+OK" or "-ERR"
`
` RETR mailbox
`
` This command begins a mail reading transaction. The RETR
` command is used to read all the messages in a mailbox without
` deleting them. It must be followed by the RCEV command.
`
` Possible responses: "#xxx" or "-ERR"
`
` RDEL mailbox
`
` This command begins a mail reading transaction. The RDEL
` command is used to read all the messages in a mailbox and
` delete them. It must be followed by the RCEV command.
`
` Possible responses: "#xxx" or "-ERR"
`
` RCEV
`
` This command confirms that the client is ready to receive the
` mail data. It must be followed by the RCVD command.
`
` Possible responses: "+OK" or (connection aborted)
`
` RCVD
`
` This command confirms that the client has received and accepted
` the mail. The RCVD command ends the mail reading transaction.
` In the case of the RDEL transaction, it is possible that the
` mail is not necessarily deleted. This is indicated by an error
` reply.
`
` Possible responses: "+OK" or "-ERR"
`
`Reynolds [Page 3]
`
`CODE200 ET AL. EXHIBIT 1026
`Page 3 of 5
`
`

`

`
`Post Office Protocol RFC 918
`
` QUIT
`
` This command indicates the client is done with the session.
` The server sends an OK response and then closes the connection.
`
` Possible responses: "+OK" then Close
`
` NOOP
`
` This is the no operation command. It causes no action on the
` part of the server except an OK response.
`
` Possible response: "+OK"
`
` RSET
`
` This command causes the server to abort the current transaction
` and return to waiting for a command (one of RDEL, RETR, QUIT,
` NOOP, or RSET). When aborting a transaction the server must
` take care to properly close and unlock the mailbox.
`
` Possible response: "+OK"
`
`Acknowledgment
`
` I would like to acknowledge the contributions of Jon Postel, Joel
` Goldberger, Dale Chase, and Michael Butler in the development of the
` Post Office Protocol.
`
`References
`
` [1] Postel, J., "Simple Mail Transfer Protocol", RFC-821,
` USC/Information Sciences Institute, August 1982.
`
` [2] Crocker, D., "Standard for the Format of ARPA-Internet Text
` Messages", RFC-822, University of Delaware, August 1982.
`
`Reynolds [Page 4]
`
`CODE200 ET AL. EXHIBIT 1026
`Page 4 of 5
`
`

`

`
`Post Office Protocol RFC 918
`
`Diagram
` +---+ +---+ +---+ +---+ +---+
` Open | | +OK | | | | +OK | | | | +OK
` ----->| S |--+-->| C |------>| S |------>| C |------>| S |---->+
` | | ^ | | USER | | | | PASS | | |
` +---+ | +---+ +---+ +---+ +---+ |
` | | -ERR | -ERR |
` | V V |
` +<-----------+<----------------+<----------------------+ |
` | |
` V +---+ +---+ |
` +----->| | QUIT | | +OK |
` | C |------>| S |----->Close |
` +----->| | | | |
` ^ +---+ +---+ |
` | V
` +<-------------------------------------------------------------+
` | ^
` | +---+ +---+ +---+ +---+ +---+ +---+ |
` | | |RETR | | #xxx | |RECV | |DATA | |RCVD | |+OK |
` +->| C |---->| S |----->| C |---->| S |---->| C |---->| S |--->+
` | | | or | | | | | | | | | | ^
` | +---+ RDEL+---+ +---+ +---+ +---+ +---+ |
` | | -ERR | | | | -ERR |
` | V | V | | |
` +<-------------+ | Abort | | |
` | V V V |
` | +<---------------+-------------------+ +----->+
` | V
` | +---+ +---+
` | | | RSET | | +OK
` +----->| C |------>| S |----->+
` | | | | | |
` | +---+ +---+ |
` | V
` +<----------------------------+
` | ^
` | +---+ +---+ |
` | | | NOOP | | +OK |
` +----->| C |------>| S |----->+
` | | | |
` +---+ +---+
`
`Reynolds [Page 5]
`
`CODE200 ET AL. EXHIBIT 1026
`Page 5 of 5
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket