IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Sun, 26 May 2019 16:53 UTC

Return-Path: <johnl@taugh.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 974BC1200D5 for <dmarc@ietfa.amsl.com>; Sun, 26 May 2019 09:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 header.b=Me1L+q+R; dkim=pass (1536-bit key) header.d=taugh.com header.b=CyaPM/V/
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 52dGTx5eTmCt for <dmarc@ietfa.amsl.com>; Sun, 26 May 2019 09:53:18 -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 6449E1200CD for <dmarc@ietf.org>; Sun, 26 May 2019 09:53:18 -0700 (PDT)
Received: (qmail 23523 invoked from network); 26 May 2019 16:53:16 -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=5be1.5ceac47c.k1905; i=johnl-iecc.com@submit.iecc.com; bh=ySeJG6GZk+zCYW4jkTHrkRapfCEtjPTpP9Htj68C/Ew=; b=Me1L+q+R9l5BpLweWgJnYP43Dzi8AME2EBRtBv48tL1DK77/I9xaKCOtEPN2ctEGVhCxFCCwKW5Gu2c11UjcT63O/CpTq/YLmK6wyEf0Vxa0Svi8kHieotQ/IW2ceX6Bwteg6fY8Y230egD0A104/nFcKodHd862LQN1tMx90lvSP7VouRADqwqm1Kl+kL1kdeVV3hV2sIGy5HZRbc/yVKRMdBgRrDy/PLxpSEGETBd8UgC7u4a5I0KOXwkfyNaz
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=5be1.5ceac47c.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=ySeJG6GZk+zCYW4jkTHrkRapfCEtjPTpP9Htj68C/Ew=; b=CyaPM/V/rauRzW8zSQgr0d9hBtbWor+7HJH3fzhyCm6BnGyCu3VoXnTD0nt+HEBTrtYmHiQLNfac38Dbqaxylb7F5U0/u+uiG9mzVl+edkeq4a2YesnwZccA2TzQYJ50hLG4uzMGbnKdENgdayosgSyVu38knAhePyLruHBwXIFC/tI5shBV+N6ag+pN7NYWWOIIKmkosC8IRYYNDvmsT+6MeAxP/yDhTsn2ZPa9eXzE5WXGtJwc1SDK0OczL1C4
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; 26 May 2019 16:53:16 -0000
Date: Sun, 26 May 2019 12:53:15 -0400
Message-ID: <alpine.OSX.2.21.9999.1905261252270.58647@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Dotzero <dotzero@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <CAJ4XoYfga+aX8J+aap6hN+EkZ=OrU0DnAXaCbqBjTwv3fAWUfA@mail.gmail.com>
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> <4e4a59d7-e652-48f1-feb1-09d948c3eb04@bluepopcorn.net> <CAJ4XoYfga+aX8J+aap6hN+EkZ=OrU0DnAXaCbqBjTwv3fAWUfA@mail.gmail.com>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Dly0Eh3zAQJuUk-h0Qnd8o8WeAc>
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: Sun, 26 May 2019 16:53:21 -0000

On Sun, 26 May 2019, Dotzero wrote:

>>> 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

>> I think you are underestimating the deployment. Many receiving/validating
>> organizations have privacy concerns about promiscuously disseminating
>> reports. As a result, these organizations limit reports to senders with
>> which they have either direct contractual relationships or intermediaries
>> with which they have contractual relationships. Personally I would prefer
>> to see more and better reporting but I recognize the issues involved. It's
>> important to recognize that senders publishing DMARC records are indicating
>> their policy preferences to receivers which choose to validate for DMARC.
>> Receivers which choose to validate DMARC are not required to provide
>> records in response to sender requests. I know that reporting is valuable
>> for senders and to the extent possible we should be finding ways to
>> encourage and support reporting.

Still sounds like a deployment guide would be useful, no?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email