RFC 2476: Message Submission

In plain English — editorial summary, not part of the RFC

This memo describes a low cost, deterministic means for messages to be identified as submissions, and specifies what actions are to be taken by a submission server. [STANDARDS-TRACK]

Document record

Document ID

RFC2476

Published

December 1998

Authors

R. Gellens; J. Klensin

Status

PROPOSED STANDARD

Stream

Legacy

Area

—

Pages

15

Also known as

—

Obsoleted by:

RFC 4409

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC2476

Topics

• SMTP
• simple mail transfer protocol
• user
• agent

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

1. RFC 2476 (1998)
2. →RFC 4409 (2006)
3. →RFC 6409 (2011) ✓

Read the full history of Message Submission for Mail →

Referenced by

One later RFC formally updates or obsoletes part of this document.

• RFC 4409Message Submission for MailObsoleted

  April 2006

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 2852Deliver By SMTP Service ExtensionCurrent

  June 2000

• RFC 3030SMTP Service Extensions for Transmission of Large and Binary MIME MessagesCurrent

  December 2000

• RFC 3207SMTP Service Extension for Secure SMTP over Transport Layer SecurityUpdated

  February 2002

• RFC 2821Simple Mail Transfer ProtocolObsoleted

  April 2001

• RFC 1803Recommendations for an X.500 Production Directory ServiceCurrent

  June 1995

• RFC 3463Enhanced Mail System Status CodesUpdated

  January 2003

• RFC 3848ESMTP and LMTP Transmission Types RegistrationCurrent

  July 2004

• RFC 3865A No Soliciting Simple Mail Transfer Protocol (SMTP) Service ExtensionCurrent

  September 2004

Also filed under

• PROPOSED STANDARD
• 1998
• Legacy stream