RFC 6650: Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)
In plain English — editorial summary, not part of the RFC
RFC 5965 defines an extensible, machine-readable format intended for mail operators to report feedback about received email to other parties. This applicability statement describes common methods for utilizing this format for reporting both abuse and authentication failure events. Mailbox Providers of any size, mail-sending entities, and end users can use these methods as a basis to create procedures that best suit them. Some related optional mechanisms are also discussed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6650
- Published
- June 2012
- Authors
- J. Falk; M. Kucherawy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 15
- Also known as
- —
- Updates:
- RFC 5965
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6590Redaction of Potentially Sensitive Data from Mail Abuse ReportsCurrent
April 2012
- RFC 6449Complaint Feedback Loop Operational RecommendationsCurrent
November 2011
- RFC 6651Extensions to DomainKeys Identified Mail (DKIM) for Failure ReportingCurrent
June 2012
- RFC 6652Sender Policy Framework (SPF) Authentication Failure Reporting Using the Abuse Reporting FormatCurrent
June 2012
- RFC 6686Resolution of the Sender Policy Framework (SPF) and Sender ID ExperimentsCurrent
July 2012
- RFC 6609Sieve Email Filtering: Include ExtensionCurrent
May 2012
- RFC 6591Authentication Failure Reporting Using the Abuse Reporting FormatUpdated
April 2012
- RFC 6715vCard Format Extensions: Representing vCard Extensions Defined by the Open Mobile Alliance (OMA) Converged Address Book (CAB) GroupCurrent
August 2012
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?