IETF Logo Mail Archive

Re: [dmarc-ietf] Endless Email Loops with Aggregate Reports

Alexey Melnikov <aamelnikov@fastmail.fm> Sat, 01 June 2019 09:01 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 024EC120222 for <dmarc@ietfa.amsl.com>; Sat, 1 Jun 2019 02:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=fastmail.fm header.b=qASsMkcc; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=t/GJ6UL8
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 qrX_JZaxe0UL for <dmarc@ietfa.amsl.com>; Sat, 1 Jun 2019 02:01:10 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95EA11201D1 for <dmarc@ietf.org>; Sat, 1 Jun 2019 02:01:10 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 99F3321FFD; Sat, 1 Jun 2019 05:01:09 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Sat, 01 Jun 2019 05:01:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=h HcJPEiOPJDu+WIfCGUfPfG1jGKGhXRzeMO9Vg5kdKg=; b=qASsMkccyPgwuQevw h7tU5kK19NU/D3+rgFaZuxRswHS5wDZPi2tdb+kW23B/39S+vN2H+BnEFkyyUr9r QVD3LUg6AWSTAqk78yApyhRRA+htTMA0u4sKei6E5uPle/wbHWDwSgdCxVkzkp/V NMYftlvU+LVlDPhzVjnorfHzn2/pqJb2Z70h2IC/hgeJVnBiAOEcBbXZTqMnJ9oN Pb2tknc2j2xcab66AismhZeBK0moVMqJ9/wBmnIydYsaO+d8cOvpJD70OaFjBADn GmGd2zCsLGwuRa33DmiBlwQCcaioq+oy/jcLMlq5ZUAAUHX2yOFx1aEEtbZaZlTF Mb2uQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=hHcJPEiOPJDu+WIfCGUfPfG1jGKGhXRzeMO9Vg5kd Kg=; b=t/GJ6UL83P+vJQBCWRCLXavNoyp5yXU2PRVGDo7VWU6M8dBNn2MG+Cngj lHdkH86WLhG3O/wYLF8m+qMkxRtKeG6yPvq1SlPQZ7tA1gplMBq/J5TLKewjbvY1 K+n2PyeisGzFxmKFVeoUtHseHII2zpVV/G/kbVz1PmMvVG/QqnrquoKJl51CwS2n 7TkdklmdLSmEc81V7QuzBzgjD+0eDaULV5FsjggVyvdOSFXgv+Izcaoo9xaIxfmL AtlFWA6zOWJSxtbDJKppwvBu5Onge7E3765t3DSslD95ih+7fWGw74ZBo9YdzNaz 66oRiMJTugJDIwqg77e57og4wGVrw==
X-ME-Sender: <xms:zj7yXIz3rwxpffriQl23_0zN2llKP9En8sCEnRFJ4hHbEtm1vN4ugA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeffedguddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhofgjfffgkfhfvfesthhqmhdthhdtjeenucfhrhhomheptehlvgig vgihucfovghlnhhikhhovhcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh eqnecuffhomhgrihhnpehivghtfhdrohhrghdpsggsihifrdhnvghtnecukfhppeejjedr leejrddugeehrdehheenucfrrghrrghmpehmrghilhhfrhhomheprggrmhgvlhhnihhkoh hvsehfrghsthhmrghilhdrfhhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:zj7yXDKqxYbe_WM9BQ_SMPtu4oFfmrzYp0IF2UhSQULTHKXm1jiJyA> <xmx:zj7yXHTku0UXo-Ewm2MueWUY6WUbHTPGOUMc_3gryB_BK04nLyLlwA> <xmx:zj7yXDqHAyERBG771zOWnk36vmKsXqOlQ6ojjbSXywGzar8KIb6aVg> <xmx:1T7yXLLK3V9KTfSPKJ9TYkuDnGR_Cwmt3EEnGrWoYKt4NL52oxpvsQ>
Received: from [192.168.0.12] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F80080059; Sat, 1 Jun 2019 05:01:01 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPad Mail (16D57)
In-Reply-To: <f5c5ea46-71ec-4fdd-36bb-fce37271d894@dcrocker.net>
Date: Sat, 01 Jun 2019 10:00:59 +0100
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, Dilyan Palauzov <Dilyan.Palauzov@aegee.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B21CC6FB-2F2C-4AA6-8DAA-05B026DF0E4E@fastmail.fm>
References: <20190531175532.Horde.UpMFNBGKjRWB_hCZWHwSUfK@webmail.aegee.org> <CAL0qLwZpCmOV58Zc=ALJzfTsX-4F=5=d882+RYyRXFvkhb4PSQ@mail.gmail.com> <f5c5ea46-71ec-4fdd-36bb-fce37271d894@dcrocker.net>
To: dcrocker@bbiw.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/IJKgtLlQD1bCB7OHOCqB6DCe5r8>
Subject: Re: [dmarc-ietf] Endless Email Loops with Aggregate Reports
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: Sat, 01 Jun 2019 09:01:13 -0000

Hi Dave,

> On 1 Jun 2019, at 09:18, Dave Crocker <dhc@dcrocker.net> wrote:
> 
>> On 6/1/2019 10:13 AM, Murray S. Kucherawy wrote:
>> On Fri, May 31, 2019 at 10:55 AM Dilyan Palauzov <Dilyan.Palauzov@aegee.org <mailto:Dilyan.Palauzov@aegee.org>> wrote:
>>    Shall I submit an erratum to RFC7489?
>> I would, yes.  And this should certainly be recorded as something we need to fix for standards track DMARC, whether by chasing down RFC7489 errata or via a dedicated issue in this WG's tracker.
> 
> Hmmm...
> 
> The formal rule for errata in the RFC system is rather constrained: Only errors that mis-specify what was intended are permitted.
> 
> So, errors in thinking or failures to provide for cases don't count as errata.

You are right, but I can always mark this issue as “hold for update”, so that it can be tracked for the -bis document.

Best Regards,
Alexey
> 
> What this means is that there is no standard way to record the need for better-performing capabilities or addition of new capabilities or the like.
> 
> d/
> 
> 
> -- 
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
> 
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc

v2.23.0 | Report a Bug | By Email