IETF Logo Mail Archive

Re: [dmarc-ietf] DMARCbis issue: what is DMARC ?

"John R. Levine" <johnl@iecc.com> Tue, 28 May 2019 15:22 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13793120173 for <dmarc@ietfa.amsl.com>; Tue, 28 May 2019 08:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rKmPAjyRZYG for <dmarc@ietfa.amsl.com>; Tue, 28 May 2019 08:22:15 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B86351200D6 for <dmarc@ietf.org>; Tue, 28 May 2019 08:22:14 -0700 (PDT)
Received: (qmail 91697 invoked from network); 28 May 2019 15:22:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1662e.5ced5224.k1905; i=johnl-iecc.com@submit.iecc.com; bh=wfnboyXT8f6kxtRqKbqtdNR8prQGdtShY6Vnt3lI3VI=; b=dMWmp6xF/VhHSOFhDDyH8PX20CN2TJCeX2nPEnAMdUaI8MYEhZitkoAtJpbqbFGNDKOqL8Ai6xQkSf5BMY1MvKSeIIaWTCcq7eiQYIbNlN96tFcTpdilyD+uAcqxb69ov1iBVBDBXsVX4VDRSh0FDmXnH/25XwOV+TF4khw7JV6oTzD6t4ZUTTZfGCW6u1GxDhy8UBJJa1PcDT0zErer+LxJozRzP2bZ32MHGiK6zLvv+cWW4p943peBv2/SihpB
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 28 May 2019 15:22:12 -0000
Date: Tue, 28 May 2019 11:22:11 -0400
Message-ID: <alpine.OSX.2.21.9999.1905281120350.67418@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: dmarc@ietf.org
In-Reply-To: <384aaed3-414f-5d1b-0d20-90a5f25597f2@tana.it>
References: <20190523225213.C214620147B780@ary.qy> <ab587c42-dd2f-2403-999a-c7d559764726@bluepopcorn.net> <alpine.OSX.2.21.9999.1905241036450.50141@ary.qy> <280824a0-536b-91f1-8072-f7d1cf3051aa@bluepopcorn.net> <alpine.OSX.2.21.9999.1905241416240.51329@ary.qy> <384aaed3-414f-5d1b-0d20-90a5f25597f2@tana.it>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-190567311-1559056932=:67418"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/9E4A6Ki6LVMm5ADkWPDvrx4_xs8>
Subject: Re: [dmarc-ietf] DMARCbis issue: what is DMARC ?
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2019 15:22:17 -0000

>> Deploying DMARC seems to mean any subset of these:
>>
>> 1a.  Publish a DMARC record
>> 1b.  Publish a DMARC record with a restrictive policy
>> 2a.  Evaluate DMARC status of incoming messages
>> 2b.  Use that status to manage message disposition
>> 3.   Collect reports
>> 4a.  Send aggregate reports
>> 4b.  Send failure reports
>
>
> Nice one!  That analysis should make it to some implementation guide.  I'd
> suggest an addition, though:
>
> 3a.  Receive and possibly read records
> 3b.  Collect them

As far as DMARC is concerned, once you've published rua or ruf and receive 
the reports, DMARC is done.  Some people just put them in a mailbox, some 
pick out basic bits and put them in a database, some do elaborate 
analyses, but none of that has anything to do with DMARC compliance.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email