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

Deletion and UPDATE

04

DELE marks a message; QUIT from the transaction requests actual deletion processing.

Related RFCs and changes

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

DIAGRAM§ 6 ↗
RFC 1939 · § 6EXAMPLE
3 / 3
Deletion and UPDATEDELE marks a message; QUIT from the transaction requests actual deletion processing.Deletion and UPDATESeparate QUIT: UPDATEOrderly UPDATE processes deletion marks
03
Separate orderly QUIT

In an orderly transaction, QUIT enters UPDATE and processes the marked deletions.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

RSET can clear deletion marks during transaction.

  • RSET can clear deletion marks during transaction.
  • Abnormal disconnect does not enter UPDATE and must not remove messages.
  • UPDATE errors can leave some or none of the marked messages deleted, within the specified constraints.
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 ↗