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

Flags and deletion

04

Flags describe server-side message state; deletion marking and expunging are separate operations.

Related RFCs and changes

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

RFC 9051 · § 2.3.2EXAMPLE
3 / 3
Flags and deletionFlags describe server-side message state; deletion marking and expunging are separate operations.Flags and deletionExpunged from mailboxDeletion marking and removal are separate
03
Expunge

The marked message is removed and sequence positions can change.

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

STORE can update flags such as Seen or Deleted under mailbox permissions.

  • STORE can update flags such as Seen or Deleted under mailbox permissions.
  • Marking Deleted alone does not necessarily remove a message.
  • EXPUNGE permanently removes messages marked Deleted under the command rules.
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. Session and mailbox states
  2. UIDs versus sequence numbers
  3. Selective FETCH and SEARCH
  4. Flags and deletion
  5. Unsolicited updates and resync
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗