Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality

Alessandro Vesely <> Thu, 21 January 2021 10:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 65E0E3A186E for <>; Thu, 21 Jan 2021 02:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Status: No, score=-2.382 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, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1152-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fiRzcMJjTPCr for <>; Thu, 21 Jan 2021 02:06:29 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 95D803A186C for <>; Thu, 21 Jan 2021 02:06:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=delta; t=1611223587; bh=vgHvNnAGdEIde6/hYA7kAfmp7NQ4lpQtBMH8E+sDLxw=; l=1494; h=To:References:From:Date:In-Reply-To; b=BZEurB5+QgQEknDPmgoopS5YdqwtnNZpWjJNELzz36wHfLamYG9VP+53d79afEZey sl9+QDWTd3v09AAz2B1tlofpdkQ5OAxKctNG91xwuKkLlOeg0vh1pXVAij7K5kwP96 siSimEd61ppFiwVf6f3UwhZSx5IiwcsCRAoZZDrsivjZzyf/ILMJzVYlLmncG
Authentication-Results:; auth=pass (details omitted)
Original-From: Alessandro Vesely <>
Received: from [] (pcale.tana []) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by with ESMTPSA id 00000000005DC0CC.0000000060095223.000076EE; Thu, 21 Jan 2021 11:06:27 +0100
References: <20210120023151.3C86A6B7C86C@ary.qy> <> <> <> <>
From: Alessandro Vesely <>
Message-ID: <>
Date: Thu, 21 Jan 2021 11:06:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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: Thu, 21 Jan 2021 10:06:31 -0000

On Thu 21/Jan/2021 01:05:53 +0100 Michael Thomas wrote:
> On 1/20/21 3:10 PM, Steven M Jones wrote:
>> I think we should specify HTTPS URIs, and following 7489 section 12.6
>> "Secure Protocols" and current practices, HTTP should not be
>> specified/permitted.
>> However I don't yet see a compelling case for the OR- syntax or a
>> separate "ruap" tag. Duplicate reports to the same destination are not
>> the base case, and the bandwidth for unintended duplicates will likely
>> be much smaller than, say, per-message DNS tree walks being discussed
>> elsewhere. Report processors annoyed by receiving duplicates can work
>> with the domain owners in question, and if that doesn't work they can
>> withdraw their report authorization record.

The point is that if you specify both mailto: and https:, a compliant report 
generator should send to both URLs.  OTOH, if you only specify https:, you are 
going to miss a lot of reports.

> See this before spending too much time. It's probably better to just junk this 
> enhancement.

The proposed workaround implies sending base64, which is what https: is meant 
to avoid.  Your suggestion to use it as an authentication mechanism for https: 
sounds better.  You just need to add From: and DKIM-Signature: header fields, 
where the binary body is hashed as-is, that is, with no canonicalization.  It 
seems to require an easy software enhancement.