RFC 3865: A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension
In plain English — editorial summary, not part of the RFC
This document proposes an extension to Soliciting Simple Mail Transfer Protocol (SMTP) for an electronic mail equivalent to the real-world "No Soliciting" sign. In addition to the service extension, a new message header and extensions to the existing "received" message header are described. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3865
- Published
- September 2004
- Authors
- C. Malamud
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent
July 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
- RFC 3463Enhanced Mail System Status CodesUpdated
January 2003
- RFC 2821Simple Mail Transfer ProtocolObsoleted
April 2001
- RFC 3207SMTP Service Extension for Secure SMTP over Transport Layer SecurityUpdated
February 2002
- RFC 3030SMTP Service Extensions for Transmission of Large and Binary MIME MessagesCurrent
December 2000
- RFC 2852Deliver By SMTP Service ExtensionCurrent
June 2000
- RFC 2476Message SubmissionObsoleted
December 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?