API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5068
[ACTIVE]

Email Submission Operations: Access and Accountability Requirements

Metadata

Publisher
IETF
Doc Type
Best Practice
Pages
12
Abstract
Email has become a popular distribution service for a variety of socially unacceptable, mass-effect purposes. The most obvious ones include spam and worms. This note recommends conventions for the operation of email submission and transport services between independent operators, such as enterprises and Internet Service Providers. Its goal is to improve lines of accountability for controlling abusive uses of the Internet mail service. To this end, this document offers recommendations for constructive operational policies between independent operators of email submission and transmission services. Email authentication technologies are aimed at providing assurances and traceability between internetworked networks. In many email services, the weakest link in the chain of assurances is initial submission of a message. This document offers recommendations for constructive operational policies for this first step of email sending, the submission (or posting) of email into the transmission network. Relaying and delivery entail policies that occur subsequent to submission and are outside the scope of this document. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date
2007-11-01
Status Note
Best Current Practice
DOI
10.17487/RFC5068
Link
https://doi.org/10.17487/RFC5068
Author(s)
Carl Hutzler
Dave Crocker
Pete Resnick
Eric P. Allman
Tony Finch
Keyword(s)
Spam, Email Abuse, Phishing, Email, MIME, IMF, RFC 822, SMTP, RFC 821, Architecture, MTA, MUA, MSA, MDA, Delivery, Gateway Agent, Sieve, DSN, MDN, MHS, Mail Handling Service, Mail Submission Agent, Mail Delivery Agent
Latest version of IETF RFC 5068

Document Versions — IETF RFC 5068

  • ▶ IETF RFC 5068 (2007-11-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5068.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5068, Email Submission Operations: Access and Accountability Requirements. Available at https://doi.org/10.17487/RFC5068
Snippet:
IETF RFC 5068, Email Submission Operations: Access and Accountability Requirements. Available at https://doi.org/10.17487/RFC5068

HTML (ISO 690 compliant)

Preview:
IETF RFC 5068, Email Submission Operations: Access and Accountability Requirements. Available at https://doi.org/10.17487/RFC5068
Snippet:
<span class="citation"><cite>IETF RFC 5068</cite>, Email Submission Operations: Access and Accountability Requirements. Available at <a href="https://doi.org/10.17487/RFC5068" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5068</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5068, Email Submission Operations: Access and Accountability Requirements
doi: 10.17487/RFC5068
url: https://doi.org/10.17487/RFC5068
Snippet:
<li>
<cite id="bib-rfc5068">IETF RFC 5068</cite>, Email Submission Operations: Access and Accountability Requirements
<span class="doi">10.17487/RFC5068</span>
</li>

Referenced By