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

Alessandro Vesely <vesely@tana.it> Tue, 19 January 2021 19:18 UTC

Return-Path: <vesely@tana.it>
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 865173A16E8 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:18:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 o0GjuwN6Plhk for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:18:33 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 D79263A16E3 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:18:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611083908; bh=cQwZLF/PhhTGFz5Dz2Iolt64B0Mvr4WLYnZuKBSyKPM=; l=569; h=To:References:From:Date:In-Reply-To; b=CptSdF3M9TbPXV4m+OuJWDSTiKF60quaIpcEGej8c2jSGTLzsezqxNbrVQyNCLVJS qS6jTTq5XjrpYFMSka/CUQSb4xgV4NqnaTaEycmFPS4IwYEL1x2t9uSkPln+tqWn9Z JXtcgrsYA9VBjnYQtZ3256zaBoUC79/T6/AUwFtKhM+T4mpPYVPXmdzA+0BMv
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC056.0000000060073084.00005DAF; Tue, 19 Jan 2021 20:18:28 +0100
To: Todd Herr <todd.herr@valimail.com>, IETF DMARC WG <dmarc@ietf.org>
References: <eb3d06f-c89f-2511-3528-d421473e4d42@taugh.com> <a67a4e98-2be0-e2e2-2595-c12d9b87c4df@taugh.com> <7d3be6c4-aa17-3c34-d8f0-4df51e46ccc1@tana.it> <f12991fe-fded-6c0-528c-3b879b4a670@taugh.com> <8b6605de-ca01-904c-de78-deae254e0891@tana.it> <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <d7b0a494-e9f8-4765-2b47-65d299305b41@tana.it>
Date: Tue, 19 Jan 2021 20:18: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: <CAHej_8nwEh8SXN1_WJ-QRFCZ1bUEDb1H3w-5WoB=wRcL_NzYcw@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RcGF_4msY6m-bf2rJ09xKh3ax2I>
Subject: Re: [dmarc-ietf] Ticket #42 - Expand DMARC reporting URI functionality
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, 19 Jan 2021 19:18:35 -0000

On Tue 19/Jan/2021 15:02:39 +0100 Todd Herr wrote:
> Concerns were voiced about interoperability impacts for Ale's suggestions,
> and Ale committed to running an experiment to see if there were changes to
> his inbound report flows when he implemented one variant for expressing the
> URI in the rua tag (v=DMARC1; p=none; rua=mailto:local@example.com, 
> mailto:report@service.example, OR-https://service.example/report/;), but
> there have been no subsequent posts by him to the list to report on
> results.


It seems to work perfectly.


Best
Ale
--