RFC 5863 Informational Authentication

DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations

DomainKeys Identified Mail (DKIM) allows an organization to claim responsibility for transmitting a message, in a way that can be validated by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. A message can contain multiple signatures, from the same or different organizations involved with the message. DKIM defines a domain-level digital signature authentication framework for email, using public key cryptography and using the domain name servic

Status
Informational. Published for the record and carrying no standards weight. Worth knowing before citing it as a requirement.
Published
May 2010
Authors
T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker
Read it
rfc-editor.org · DOI

Informational, not a standard. Published for the record and carrying no standards weight. Worth knowing before citing it as a requirement.

Normative requirements

Every sentence in this RFC carrying an RFC 2119 keyword, with the section it came from. 1 must, 0 should, 1 may.

2.2 Choosing a DKIM Tag for the Assessment Identifier

  • MAYDKIM MAY optionally provide a single responsible Agent or User Identifier (AUID)...
  • MUSTA receive-side DKIM verifier MUST communicate the Signing Domain Identifier (d=) to a consuming Identity Assessor module and MAY communicate the User Agent Identifier (i=) if present....

Every current email RFC