RFC 7489 on Domain-based Message Authentication, Reporting, and Conformance (DMARC)

rfc-editor@rfc-editor.org Wed, 18 March 2015 20:06 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id DC7EF1A1B92 for <ietf-announce@ietfa.amsl.com>; Wed, 18 Mar 2015 13:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id B3HUs723dvuj for <ietf-announce@ietfa.amsl.com>; Wed, 18 Mar 2015 13:06:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 8B09A1A1B67 for <ietf-announce@ietf.org>; Wed, 18 Mar 2015 13:06:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 23F9B18020A; Wed, 18 Mar 2015 13:04:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7489 on Domain-based Message Authentication, Reporting, and Conformance (DMARC)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150318200459.23F9B18020A@rfc-editor.org>
Date: Wed, 18 Mar 2015 13:04:59 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/KDU7XE6y9w2IgRHYJ5wLI7lIy8g>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2015 20:06:11 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7489

        Title:      Domain-based Message Authentication, Reporting, and 
                    Conformance (DMARC) 
        Author:     M. Kucherawy, Ed.,
                    E. Zwicky, Ed.
        Status:     Informational
        Stream:     Independent
        Date:       March 2015
        Mailbox:    superuser@gmail.com, 
        Pages:      73
        Characters: 162707
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-kucherawy-dmarc-base-12.txt

        URL:        https://www.rfc-editor.org/info/rfc7489

Domain-based Message Authentication, Reporting, and Conformance
(DMARC) is a scalable mechanism by which a mail-originating
organization can express domain-level policies and preferences for
message validation, disposition, and reporting, that a mail-receiving
organization can use to improve mail handling.

Originators of Internet Mail need to be able to associate reliable
and authenticated domain identifiers with messages, communicate
policies about messages that use those identifiers, and report about
mail using those identifiers.  These abilities have several benefits:
Receivers can provide feedback to Domain Owners about the use of
their domains; this feedback can provide valuable insight about the
management of internal operations and the presence of external domain
name abuse.

DMARC does not produce or encourage elevated delivery privilege of
authenticated email.  DMARC is a mechanism for policy distribution
that enables increasingly strict handling of messages that fail
authentication checks, ranging from no action, through altered
delivery, up to message rejection.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC