Visual RFC.
ALL RFCs / RFC 1939
Read the RFC ↗
RFC 1939 / MECHANISM GUIDE

POP3 session states

01

A POP3 session advances through authorization, transaction, and update.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3 ↗
RFC 1939 · § 3EXAMPLE
3 / 3
POP3 session statesA POP3 session advances through authorization, transaction, and update.POP3 session statesAUTHORIZATIONauthenticateTRANSACTIONQUITUPDATE
03
QUIT to update

The server applies deletion processing and ends the session.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 1725RFC 1939 Appendix A

This revision makes USER and PASS optional, requires uppercase +OK/-ERR status indicators, and clarifies command handling.

Read the updated RFC section ↗
KEY POINT

A successful greeting begins the authorization phase.

  • A successful greeting begins the authorization phase.
  • After authentication and maildrop locking, transaction commands become available.
  • Only QUIT from transaction enters update.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. POP3 session states
  2. List and retrieve messages
  3. Stable identifiers with UIDL
  4. Deletion and UPDATE
  5. Authentication and transport limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗