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

Authentication and transport limits

05

This historical specification includes authentication mechanisms that do not provide modern transport confidentiality.

Related RFCs and changes

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

DIAGRAM§ 13 ↗
RFC 1939 · § 13EXAMPLE
3 / 3
Authentication and transport limitsThis historical specification includes authentication mechanisms that do not provide modern transport confidentiality.Authentication and transport limitsUSER / PASS over an unprotected hopcredentials visibleLater guidance: protect access with TLSProtected account access ≠ message authorship
03
Separate identity and retrieval

Authentication establishes account access; retrieval remains a maildrop operation.

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

USER/PASS can expose credentials without a protected channel.

  • USER/PASS can expose credentials without a protected channel.
  • The original APOP MD5 challenge-response is not a substitute for modern TLS guidance.
  • Use later mail-access security guidance when deploying POP3.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗