Re: [dmarc-ietf] Forensic report loops are a problem

Dave Crocker <> Mon, 01 February 2021 16:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CB1543A12BE for <>; Mon, 1 Feb 2021 08:38:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lZ7d-lwy4IKe for <>; Mon, 1 Feb 2021 08:38:11 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 65F2B3A10AC for <>; Mon, 1 Feb 2021 08:38:11 -0800 (PST)
Received: by with SMTP id k25so19414449oik.13 for <>; Mon, 01 Feb 2021 08:38:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=MA15fescts+Y7MUj1QbLvx6tCbKdE+BIs1TvJqwDiGE=; b=olxQ/bUfrzFr7KaJ3TFzNQ5meEiPSFusKq1X1I0i4pGIWwFlqtFQwlIYP9usJDKTVu 9fzavj0kd17bpznXV+WE5LdOub5gepLDv98/766cL6Pm6ii4OnjHsIMshkV8sPZga/kO 51dR9DSelkTUymZDOMAVPDz87k3lxChRJO07oMSQ7prOIRLhama0ilakC5eN3n8wxhc7 1wYHeRRF0Wi19hky50r0Sle0j9elHAI9K4lWmlZdCRB1JcNlXY0lUJ78bpwTJDCZtUx/ Fr+vZzWfFP4q3RcaXwNXdsDuQgFSAOWzGylVfOaVc3TLH/w7wE01iK48RXFc0Eaz9Byh VbqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=MA15fescts+Y7MUj1QbLvx6tCbKdE+BIs1TvJqwDiGE=; b=bBFS1aS6QKnH9q1NsRZltnOlXoq8lq+PDQdNlaaoc+SzY8vuoCWJXXYKXYeFdmXiyQ ed6CascFhsJC11NuQdNb6XAZ+0m4xMBFSUS7EDinBzGw9dBC+GZl1NZUVsPp49K6GoVZ yqctm9IBakACq2Jvrr+fd8rB/3swLOc14TsDU7EUZSkSSzE9MXgIi98NL4yZ6gDO3sDU rvz2t8PN0yeAaA11keWF42NfK6/a6HdxIFt20dVd8i3fO+6lmawYI16ni16H+pB+tP+c nGjVsw14KkDRq8bYwst23BFTmzIXlAwHmm7Ee8KL2h0EhHTbcxhNwg4Bz2A/5jV1cWFo PIhw==
X-Gm-Message-State: AOAM530PC/n00RgRjuj66oN8cq5Zi1CYkIq+VuooPlWstLEHdKB921WO 1n1yovSyB4fAEprUsfwsMaa+h8l1hjXVJg==
X-Google-Smtp-Source: ABdhPJyN/y/MoRIG0BSVF7jrUjLdMR4ygzB397ZZauGyYlN6dznrBEShYpuJhBnDEsy2uHunT7MfAQ==
X-Received: by 2002:aca:c60d:: with SMTP id w13mr11194633oif.26.1612197490558; Mon, 01 Feb 2021 08:38:10 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id w10sm4531567oih.8.2021. for <> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Feb 2021 08:38:09 -0800 (PST)
References: <> <20210127203714.007C86CDB9CA@ary.qy> <> <>
From: Dave Crocker <>
Message-ID: <>
Date: Mon, 1 Feb 2021 08:38:07 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------1DAEF1CFA5BA85BB45675C4C"
Content-Language: en-US
Archived-At: <>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 01 Feb 2021 16:38:13 -0000

On 1/27/2021 7:17 PM, Steven M Jones wrote:
> 3.3. Transport
>    Email streams carrying DMARC failure reports MUST conform to the
>    DMARC mechanism, thereby resulting in an aligned "pass". 

    1. I haven't been tracking discussion closely.  So if this is
    something already sufficiently well-discussed and understood and
    still landed on the above normative text, I'll apologize for re-raising.

    2. But not really, because it strikes me as a serious operational
    mistake, though a well-motivated one.

Mostly this will discourage reporting.  Legitimate reporting.

Consider the challenges to ensuring a DMARC pass.  That's a pretty high 
barrier to entry against generating reports.  It should take a very, 
very substantial record of reporting problems to justify such a barrier.


Dave Crocker

Volunteer, Silicon Valley Chapter
American Red Cross