IETF Logo Mail Archive

Re: [dmarc-ietf] Endless Loops with DKIM reports

"John R Levine" <johnl@taugh.com> Thu, 06 June 2019 10:39 UTC

Return-Path: <johnl@taugh.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 18300120086 for <dmarc@ietfa.amsl.com>; Thu, 6 Jun 2019 03:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=a4t6g24O; dkim=pass (1536-bit key) header.d=taugh.com header.b=Pb/okyir
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 tRY4mld2Txca for <dmarc@ietfa.amsl.com>; Thu, 6 Jun 2019 03:38:58 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 CE40D120158 for <dmarc@ietf.org>; Thu, 6 Jun 2019 03:38:57 -0700 (PDT)
Received: (qmail 8326 invoked from network); 6 Jun 2019 10:38:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent; s=2084.5cf8ed40.k1906; i=johnl-iecc.com@submit.iecc.com; bh=G0IBJWbWLfD8bvmYfdxF9byBTpcrk04QgslYiY3jD5c=; b=a4t6g24OpX4uYROaeeonBsICj94K36279sENAqioG1lD4CjkWkaUGmVW3LUlzGtPXXjGAayV3fRd3rjL/VdrCi6qH34B3qH71nL0LWhChjz8ordUcP8mnesu8kLOvPwLtqo6uePHzawjaq02uxwRSqtAHqt9HkLNnH8bfWKeuWvdXxsh/+rYmrM+upvg7Y/oTjx6ytEp1LqFjqZ7er1FCKcSVrIxQBqgQ2SAdUMAHk/GMIgFSZ51X5IBvoLBhZCp
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent; s=2084.5cf8ed40.k1906; olt=johnl-iecc.com@submit.iecc.com; bh=G0IBJWbWLfD8bvmYfdxF9byBTpcrk04QgslYiY3jD5c=; b=Pb/okyirguBq7EzVuym50fDAwg9/lBJSyxX34JUn1sn9BhxOMmfTJ43ZHASMGGGsF7i5UUgUKEJ4a8SEnQVf5id5nLDSHpvrEqIEwpc/N2Fl3dAFEOR0ubhpWwZVmlvWPvnqoG1t69sB+9MUabZqWBXIU9tJk72vK/tcmdDFfpK01Q7lrGXCGZ7x9H0vlkJ7vh42Xn+xxiFX/PX9a+JvtXCvsF7fr/u7iRUnufCO7CH8gqwsxR/lhAQwyBsUvHF8
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 06 Jun 2019 10:38:56 -0000
Date: Thu, 06 Jun 2019 12:38:54 +0200
Message-ID: <alpine.OSX.2.21.9999.1906061235470.2459@ary.local>
From: John R Levine <johnl@taugh.com>
To: Dave Crocker <dcrocker@bbiw.net>, dmarc@ietf.org
In-Reply-To: <b7f40e8d-ddf1-8fb4-79a6-71158e0eeb91@dcrocker.net>
References: <20190605200619.2ED512014FE9B7@ary.local> <787538c5-9032-8f4d-e3f2-7e3eeb357503@dcrocker.net> <alpine.OSX.2.21.9999.1906061003130.2459@ary.local> <b7f40e8d-ddf1-8fb4-79a6-71158e0eeb91@dcrocker.net>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gmLIDtkxO3ft_ynJ0UtfZIrQ_Yk>
Subject: Re: [dmarc-ietf] Endless Loops with DKIM 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: Thu, 06 Jun 2019 10:39:01 -0000

>> If people follow the spec there will be fewer loops, but it won't reduce 
>> the number to zero.
>
> Forgive me, but I believe there is currently no spec to follow.  Yet.  I took 
> this thread as raising the issue that there needs to be an effort that 
> specifies how to avoid dmarc report loops.

As I thought I already said a few times, it would be a fine idea to offer 
advice to make DMARC reports less loop-prone.  No, that will not prevent 
all loops so you need to do rate limiting, too.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email