RFC 6377: DomainKeys Identified Mail (DKIM) and Mailing Lists
In plain English — editorial summary, not part of the RFC
DomainKeys Identified Mail (DKIM) allows an ADministrative Management Domain (ADMD) to assume some responsibility for a message. Based on deployment experience with DKIM, this document provides guidance for the use of DKIM with scenarios that include Mailing List Managers (MLMs). This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6377
- Published
- September 2011
- Authors
- M. Kucherawy
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- art
- Pages
- 26
- Also known as
- BCP167
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 9057Email Author Header FieldCurrent
June 2021
- RFC 5322Internet Message FormatUpdated
October 2008
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
- RFC 6647Email Greylisting: An Applicability Statement for SMTPCurrent
June 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?