IETF Logo Mail Archive

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

"Murray S. Kucherawy" <superuser@gmail.com> Sat, 01 June 2019 15:38 UTC

Return-Path: <superuser@gmail.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 865E5120152 for <dmarc@ietfa.amsl.com>; Sat, 1 Jun 2019 08:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 18FHZGnE9s5a for <dmarc@ietfa.amsl.com>; Sat, 1 Jun 2019 08:38:49 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 159EA12004F for <dmarc@ietf.org>; Sat, 1 Jun 2019 08:38:49 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id l26so10284977lfh.13 for <dmarc@ietf.org>; Sat, 01 Jun 2019 08:38:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VXcXk0Fnc51+PqporeL4Qc1Ocb9BTQb9RYDKAizukPc=; b=X3U58Ec35y+v3D1B+mMrVmSRL/+Jbd58IaxFZtjp/b76h0FcgS5dydGw4u5Pk0xO36 a9lz6wIm9b3uKT1n6S5vZxUr+dtvfiqhzwFSz+rGNHJ3XMIaimv8g0mH9eWJFJ01ybCW TcT1itYbUxgb/ev/w2zw3l97WAXxoe8Yj57fLth4jxt6wcQiFrebuRE2dz2LwhkcLEEC cEZKes1G7PrcKd210eIvNGmaTwN1M4GcOBNinh0qWlkGoWGs2k/FNBhTYrLoj4RQryOS +d6oXKFlkgh9ux746ZfeRYuJUvXd1psC1z4uiI7mzfF/vU0YN9Ilxt1Y4Z2vdSfbUS/S f23g==
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:cc; bh=VXcXk0Fnc51+PqporeL4Qc1Ocb9BTQb9RYDKAizukPc=; b=idKPpo9Lt/HcPU9B0AkCMa0RcH5DTO9HLsO/WRKCMjYoPAINt9cHmF3kuZKtWoJQGZ O4BcnxELSl62roiGf6qJxa7ecSMC3eu81u9pr5MMAww9Vwz2qFJ4O5cZuvohQFhJ66wR 1Hv7grpCC6m2uHlUM8zUegbG7u6Y468PEYSp29V5V2AzR5ugZjiNvgQoF4e99TRQ/l+5 RJXWDbgvDGm3Kyr57DTtLmbXuI/1saQ1qYnFwys20szXUB0lrzTAsHTK23XSfFv/Q3bM LuBVL4OB+LBuvQQBmV7j0CqOkFPdyexUP1saXEiSbM1wKGyYSgguKkcTPyXSGVpzrp40 hNyw==
X-Gm-Message-State: APjAAAVXgt7y6OD3QhdHieMeFviZ6aJ3dv++XM977e9PIYf6MvGkqSnU PWSy1lfvsKioac6CiibbdwcvaMf4mHYV8XSxVQQ=
X-Google-Smtp-Source: APXvYqyGXa8GAGfOTEJkj9hxQERrv0jIQi7Vgum1aUASjxyaqn+FJtqPlrg04/3LXkBWU14RcRU4pIBE/MTi6QwCV1U=
X-Received: by 2002:a19:ab1a:: with SMTP id u26mr1569568lfe.6.1559403527226; Sat, 01 Jun 2019 08:38:47 -0700 (PDT)
MIME-Version: 1.0
References: <20190531175532.Horde.UpMFNBGKjRWB_hCZWHwSUfK@webmail.aegee.org> <CAL0qLwZpCmOV58Zc=ALJzfTsX-4F=5=d882+RYyRXFvkhb4PSQ@mail.gmail.com> <f5c5ea46-71ec-4fdd-36bb-fce37271d894@dcrocker.net> <B21CC6FB-2F2C-4AA6-8DAA-05B026DF0E4E@fastmail.fm>
In-Reply-To: <B21CC6FB-2F2C-4AA6-8DAA-05B026DF0E4E@fastmail.fm>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sat, 01 Jun 2019 08:38:32 -0700
Message-ID: <CAL0qLwYb+giO9_HuZ2zXHTO5EgHrN+a2ssTOK+gRAx1-DZydCw@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: Dave Crocker <dcrocker@bbiw.net>, Dilyan Palauzov <Dilyan.Palauzov@aegee.org>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004d4a09058a44ed57"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ntEA1mp68d_E49k_EVpWEl-lvfQ>
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 15:38:52 -0000

On Sat, Jun 1, 2019 at 2:01 AM Alexey Melnikov <aamelnikov@fastmail.fm>
wrote:

> > 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.
>

My understanding matched Dave's originally, but then I found this:
https://www.ietf.org/blog/iesg-processing-rfc-errata-ietf-stream/

It's not surprising this sort of need to record a deficiency for later
handling has come up before, and we've adapted a way to deal with it.

-MSK

v2.23.0 | Report a Bug | By Email