IETF Logo Mail Archive

Re: [dmarc-ietf] Debugging and preventing DKIM failures- suggestion

"John R Levine" <johnl@taugh.com> Thu, 30 May 2019 21:18 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 72FF012016E for <dmarc@ietfa.amsl.com>; Thu, 30 May 2019 14:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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=K0Gb3ZQP; dkim=pass (1536-bit key) header.d=taugh.com header.b=GtU6koK3
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 xu35O5j9wmSb for <dmarc@ietfa.amsl.com>; Thu, 30 May 2019 14:18:50 -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 1448A1200E3 for <dmarc@ietf.org>; Thu, 30 May 2019 14:18:49 -0700 (PDT)
Received: (qmail 28868 invoked from network); 30 May 2019 21:18:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=70c0.5cf048b8.k1905; i=johnl-iecc.com@submit.iecc.com; bh=wkSy/Db9w2AXspF2/3SUNqrGfXTr5ulG+13boC2cFgE=; b=K0Gb3ZQPar8J9Q5nF+JPTwh9syjAEhntSfbPnjb1uGhJWCLM+UbM/w6OpEGW2KCyjBd9S/v4hsVCZ/+ik57F2tEgbOybob8mqL3AWg9OduGdjTXPRTK0lXvanNe0Tb9fuk+mKWN8utV3CFIYHprT4w3OW6b1r11pjkBsVX0CO6NYjM6VeltsaNNpWByvYspjlj4dPaBzpRIZuT9JSgeL0cHQ58DRoxVIQiD+wUMzdket1FZtk8myhDU2CBlZNZ7C
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=70c0.5cf048b8.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=wkSy/Db9w2AXspF2/3SUNqrGfXTr5ulG+13boC2cFgE=; b=GtU6koK3LD75PxqFwDP04Zixxa/ufsUNXCv4A0QuVuMqdOd7u1bMavczb8VR/KxH5WT+MkF43OuhbU/VArAK9xPlHE1R+dtuBO4NJwVBsxJUlhMIUtdPcrjx1fDEo8n7ekSBVTH9NzCFy2BYtDcx31BgmK4sjPBBVgWQSCLOu780sbfZCxXqCp7wL7buf2YWgbUujYprCj06X/tDksYrxGh2LUDEV4dXFlLM5hRmtoUdrOKpXuYfAjHfM38fJ36v
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; 30 May 2019 21:18:47 -0000
Date: Thu, 30 May 2019 17:18:47 -0400
Message-ID: <alpine.OSX.2.21.9999.1905301712140.76792@ary.qy>
From: John R Levine <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <CAL0qLwbxwLTpgYJN9qBTzi2oN1EMvAYuNoDbw5Rx5W46-WNyLA@mail.gmail.com>
References: <54FB29A0-517A-430E-AF5B-CB079CC3D7F6@aegee.org> <20190526144848.08A772014A0BF4@ary.qy> <CAL0qLwbxwLTpgYJN9qBTzi2oN1EMvAYuNoDbw5Rx5W46-WNyLA@mail.gmail.com>
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/_dkG-4WzABoI2uuOoidrOswxgOY>
Subject: Re: [dmarc-ietf] Debugging and preventing DKIM failures- suggestion
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, 30 May 2019 21:18:53 -0000

> And as John said, there have been numerous proposals over the years of ways
> to annotate a message with what "standard" mutations were done so that at
> verification time the receiver could decide which mutations it was willing
> to forgive, but the community showed no interest in such complexities.

It is my impression that the proponents of this idea tended not to be very 
familiar with mailing list software and imagined that most mutations were 
simple, like adding a subject tag or a text footer.  Those happen, but 
they are the very tip of the iceberg.  Modern list managers add, delete, 
and reorder MIME parts, flatten HTML into text, and a huge list of other 
things that no mutuation catalog could plausibly describe.

That's one of the reasons that ARC doesn't try to say what's changed, just 
what the authentication results were before and after.

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