IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Sun, 26 May 2019 14:48 UTC

Return-Path: <johnl@iecc.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 78873120135 for <dmarc@ietfa.amsl.com>; Sun, 26 May 2019 07:48:51 -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, HEADER_FROM_DIFFERENT_DOMAINS=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=vMlh4VU7; dkim=pass (1536-bit key) header.d=taugh.com header.b=3zl3IFru
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 ndGws7oRtkRr for <dmarc@ietfa.amsl.com>; Sun, 26 May 2019 07:48:49 -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 9EFFF120043 for <dmarc@ietf.org>; Sun, 26 May 2019 07:48:49 -0700 (PDT)
Received: (qmail 95532 invoked from network); 26 May 2019 14:48: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:mime-version:content-type:content-transfer-encoding; s=17528.5ceaa750.k1905; i=johnl-iecc.com@submit.iecc.com; bh=v/ya4HKGEcRkjP0IoK2IJ6mRamUHXiWFUNWslyfa+Gc=; b=vMlh4VU7e1KoKDWQ2Y+561CdrD+7+04GkTrb++XP/X46NWnVPBsDBqlKEXm1SKY6iki8pWw42496WflNnTcOQJBhjm7eUNBdtEM8n++IORl4/CpV7sFo4MU+oqZmIU6wTzx5fg3oSJbhCvfpD9fGs4vAqrFdHBkoOkKFNaqIEKLa9AW4j6O6rQQrhVh6KmvNv97MkqOijUa+ph8WRXAX3p0mInktpr1Wc/41bhhpAvH/qw3d5wS6jQdQWxnuDOfI
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=17528.5ceaa750.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=v/ya4HKGEcRkjP0IoK2IJ6mRamUHXiWFUNWslyfa+Gc=; b=3zl3IFruFFR3c8xI5fyxDUZnbZ8HzbzEjd+jM9K9lUiakBCX6pctC8+jHK5G2FAqyPibPvEwQ29mn1Rpy3G2/29u+anBpYhVq0Sdu0K/OjnUQT1OcR+BsTDv/8XBGyQe+w/GbVnmkImH4qqH/ytfNkAdzBI0BNbHh1EzZDM+DT/k8pMsOP8bYvMJ2/PD/KJIXuS3qqariFsvs9KgEsdHTgQoA/t2bgpN7vICvxOGRwgZX3TyuU4NwMLmc5d0djGl
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 26 May 2019 14:48:48 -0000
Received: by ary.qy (Postfix, from userid 501) id 08A772014A0BF4; Sun, 26 May 2019 10:48:47 -0400 (EDT)
Date: Sun, 26 May 2019 10:48:47 -0400
Message-Id: <20190526144848.08A772014A0BF4@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: Dilyan.Palauzov@aegee.org
In-Reply-To: <54FB29A0-517A-430E-AF5B-CB079CC3D7F6@aegee.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jD4WPEHrnMfspIZ2Uph9Z-T3-c0>
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: Sun, 26 May 2019 14:48:52 -0000

In article <54FB29A0-517A-430E-AF5B-CB079CC3D7F6@aegee.org> you write:
>-=-=-=-=-=-
>
>Hello Douglas,
>
>1) Check the Authentication-Results header. An implementation could put there additional information as comment. A
>downstream MTA will reevaluate the DKIM-Signature anyway, if it does nkt trust the previous hop. Common case: aliases
>to random servers.

That would be my suggestion.  You can put whatever you want into comments in the A-R header.

-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email