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

Todd Herr <todd.herr@valimail.com> Tue, 19 January 2021 19:25 UTC

Return-Path: <todd.herr@valimail.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 E57F63A1737 for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
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, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=valimail.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 4Yz__tcE2S9A for <dmarc@ietfa.amsl.com>; Tue, 19 Jan 2021 11:25:44 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519E93A1716 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:25:44 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id c7so23035779qke.1 for <dmarc@ietf.org>; Tue, 19 Jan 2021 11:25:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=cYnxNkITsSGugfrWfY53EofX511jcFAOlTQD4MuFwh4=; b=NeK/I5qc+b8IZq75rTQ9YxGqD6t5LrtDV42tB2JfgeKdsf1KLfsPEEe0e3DVoCd5q0 yicUHazy9whCuXTOyZwTOpHZ/0oaqTTkuMfwsHVktInxghz8Td2MQe8EaE10gAbKyjsW RBxnd7ds+Om/qFEU6Nwz9M6d1xkfr2uALH/oWkU0YjJk2kqSC4sWbh/nDajUMfW40GKU yZc20e8Jbw4rYxKPHsL5F6og+ZTLSsCsLhMHCDv22zaVGtSBoeHoa5DjpLwnaxXCUuXs ZMa51qxCCkpgTSY3UPAYSwWK6Ndq8jfoNMant2B4MzSVBwnrS1MweQyOPeh1QAJAVCst fWfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=cYnxNkITsSGugfrWfY53EofX511jcFAOlTQD4MuFwh4=; b=MuyGSGxeS08fBDWJdtAg9TH38e3jHcaMwDbgF3JbEYW3MqTK35WcxEidDIB7AWsEh8 39ol4E6lR6oAjICFh/YShMAOSWPgtCYiZTfCP/n/2n8uhIhmbjmAQaGSL7AAt3A5trZm oe0AO/To9GlIIhaBOq0GXfEC1P3Et/wMGqBDmmoU1/BS6hCV79MR0soTQ088HCIlp9eG uPOPwUW/RVb+FnENhbmBfOLdfLOKkFy6ZqhnHGCuJaYzbJdnNb8uo5fy0jcGLUEQENUb lP7uX9Pmdhrdg+T9DYeGRx6JgEvB7rA+h/K1IW8Hb2C6Mr8aP45ZTW/HHy16B5bR4Amf u8sA==
X-Gm-Message-State: AOAM533avsSVUqEHTVxx/vuDKwPGrQvV+VSfP+o1LNR8JFX4m6bUIiDH oFk9KoMANO/Kv26YgtobM9IiySkB6KCj04XEzNW/QLiH/s8=
X-Google-Smtp-Source: ABdhPJwYqi+DCAr2w3k6RuBCdXab7FbBb5YnQvtvIIN4NUV4rAjtcIvnyNEtZx5dGTIJvL5sEjvSyKTbDZPvoFkWnAE=
X-Received: by 2002:a05:620a:1fb:: with SMTP id x27mr2793008qkn.456.1611084343047; Tue, 19 Jan 2021 11:25:43 -0800 (PST)
MIME-Version: 1.0
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> <d7b0a494-e9f8-4765-2b47-65d299305b41@tana.it>
In-Reply-To: <d7b0a494-e9f8-4765-2b47-65d299305b41@tana.it>
From: Todd Herr <todd.herr@valimail.com>
Date: Tue, 19 Jan 2021 14:25:27 -0500
Message-ID: <CAHej_8=K_x5xOw47XBtPYBWzCbfpPSAs=i9WoweZnaa1OFc1uQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f88bc505b945cda8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/B4YnaJulcZSiW_B62cioukx7Xwo>
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:25:50 -0000

On Tue, Jan 19, 2021 at 2:18 PM Alessandro Vesely <vesely@tana.it> wrote:

> 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.
>
>
Can you provide more details, please?

Are you receiving reports by HTTPS, or have you not seen any reduction in
reports, or both, or other?

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.herr@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.