Re: [dmarc-ietf] nit - data integrity

"John Levine" <johnl@taugh.com> Sat, 15 June 2019 02:23 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 238AD120100 for <dmarc@ietfa.amsl.com>; Fri, 14 Jun 2019 19:23:39 -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_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=iGmb3hZZ; dkim=pass (1536-bit key) header.d=taugh.com header.b=INg/uWIb
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 LzTi6KFWC8iC for <dmarc@ietfa.amsl.com>; Fri, 14 Jun 2019 19:23:37 -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 3AC441200E5 for <dmarc@ietf.org>; Fri, 14 Jun 2019 19:23:37 -0700 (PDT)
Received: (qmail 88282 invoked from network); 15 Jun 2019 02:23:34 -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=158d5.5d0456a6.k1906; i=johnl-iecc.com@submit.iecc.com; bh=pDCjV/LUmQT8G1HrLxMetFEfY6R2g7+nGIOwtE6fbCI=; b=iGmb3hZZTYDyqmy/9ELEn5xNQ6zzh+KtpW0+Rc8UkBVYwr3Ld/OpOFO5l0K26/4R9wVEm8UbkyXuwyrP5NKBve6IL4MzfT/g9X/kGMOwzFBjQKuSR+I2rUuVY1l5d/vkyx3iQZsJURV4ofXk8oPhQ/PJG8oFiI33ZcqVp/Bt9IqEZEclk6R0Mtd5D1JvWtriw/kK6WVTRI4tcpKutjVbThPJZnWmob8HgZVkd/rSt9NrW121cqy9RZ9PxiobyowY
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=158d5.5d0456a6.k1906; olt=johnl-iecc.com@submit.iecc.com; bh=pDCjV/LUmQT8G1HrLxMetFEfY6R2g7+nGIOwtE6fbCI=; b=INg/uWIbGAs5j71qqN2wsTgdO84uvkrc90cKtHtAOr79mfoQaKiWb5gfvFbja3mTUIg8GCZTZZzsnn5KLNLb3v/nIYQGwtEQXumX2LzDJsmdKAMTvs6dzsamoqaDIasX+lw/VY1FanpXNhAJIjRtXzbjUt2Q41KuRtaPCp/e/BJM0w7HSClaT1Nec4qvR6r9UiFVuP9uJ8EGfVEEbivHJvsuyyHRlmd1mgpylExbU3L9InzA5k0f+GFsUEvJoss5
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; 15 Jun 2019 02:23:34 -0000
Received: by ary.qy (Postfix, from userid 501) id 4050F201561609; Fri, 14 Jun 2019 22:23:33 -0400 (EDT)
Date: 14 Jun 2019 22:23:33 -0400
Message-Id: <20190615022334.4050F201561609@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: dmarcietf@tomki.com
In-Reply-To: <0a8b5459-8a9a-7a5b-d169-4c183c43afdd@tomki.com>
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/s8Y2MRnq_K4pJvvZRgP6fIr3LS4>
Subject: Re: [dmarc-ietf] nit - data integrity
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, 15 Jun 2019 02:23:39 -0000

In article <0a8b5459-8a9a-7a5b-d169-4c183c43afdd@tomki.com> you write:
>Examples:
>- raw SPF 'fail' should never result in DMARC-SPF 'pass'
>- raw SPF 'pass' out of alignment with header_from should never result 
>in DMARC-SPF 'pass'
>- raw DKIM not being shown should never result in DMARC-DKIM 'pass'
>etc

I'm sorry, but I don't understand this at all.  The DMARC spec is
quite clear about what SPF and DKIM results are required for DMARC
alignment, and this has no connection I can see with the alignment
rules.

I also don't know what you mean by a "raw DKIM" or what it means to
show it or what you mean by "raw SPF" pass or fail.

R's,
John