Re: [dmarc-ietf] Ticket #1 - SPF alignment

John Levine <johnl@taugh.com> Sat, 30 January 2021 21:29 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 914CC3A1187 for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:29:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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=iecc.com header.b=j6sySmdP; dkim=pass (2048-bit key) header.d=taugh.com header.b=mgJzgUO/
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 AYmmgN6bhQ_Q for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:29:48 -0800 (PST)
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 F20F43A1186 for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:29:47 -0800 (PST)
Received: (qmail 3215 invoked from network); 30 Jan 2021 21:29:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=c8d.6015cfcb.k2101; bh=LyFGHx69AC+b6G6hJDOJOo0LUunlyiPEbspfn/tOwVc=; b=j6sySmdP7DCCOBaWQMIHY5R8BeBO4KvgnjPVJximZAg/uO24CV9Gs3cFlkGTTGuq9I6KUAqx5d8qQC8IUw/bNhQ/5i1f2CKj3LuSjlZCgzU31nIRVAIJs9YqMPIwoSAfqF4HbUzLdHgHL/Ai358sLGJO9tZxO8lOMHJRyXzyKiPKHL3FU7vZrF39jFX4rB+r5thj/ZUmidWWzek7UR94MBJbQgebXHFHd2WLCnRkpzXLGQExA/n5ysZ7Ih/28NYLi16LbBcK3EeAzeJFUtMBrxhBhngVHZ84gMK34Krz4cJkRRzvrXce6GCvVwiN2ReLyB9V/ydce8UlW4PcOLrR2Q==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=c8d.6015cfcb.k2101; bh=LyFGHx69AC+b6G6hJDOJOo0LUunlyiPEbspfn/tOwVc=; b=mgJzgUO/iyIzj++zrkW//tO7ASgValG5wcjsxQGhVcjh3adr4017Z7dGy5gB9QZe7o0RNCiutIKMh72rNtrOuQRKdhZAQ0/BEYyulWCDBQTuDon5aympryJosfUElGkEybFqX9ET8qHwiVW59pdqF2NB41/RgOHaqzJzfzrwbOcvJGOn1FY+sPXu0lWm/IVwdj7Pm3gQEltzcdRGN/a5NWFl+jSasMPBaYMTywUT7nP/IjDjN6GSp2qjbofJ/zBHhrLNLa3u40emChBlAU9QHPS7bY0KymCTkGkveS9qKDPoOPQ9IP8JgoSS54d0phXe2agyw6ihB9d7hy7PCFikTA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 30 Jan 2021 21:29:46 -0000
Received: by ary.qy (Postfix, from userid 501) id 62E176D0481F; Sat, 30 Jan 2021 16:29:45 -0500 (EST)
Date: 30 Jan 2021 16:29:45 -0500
Message-Id: <20210130212946.62E176D0481F@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
In-Reply-To: <20210130212339.447316D04763@ary.qy>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YKmpHJQkQ4lpWRXxfzwAkU09_jI>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
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, 30 Jan 2021 21:29:50 -0000

In article <20210130212339.447316D04763@ary.qy> you write:
>In article <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net> you write:
>>The issue isn’t the existing use of HELO names, it’s how they could 
>>be (mis-)used. The fact that a message sender can put anything there 
>>makes HELO basically meaningless.
>
>This is DMARC -- the HELO domain has to match the header From: and there
>has to be an SPF record that validates it.
>
>The most plausible case is that it's a bounce messsage
>
> From: MAILER-DAEMON@mta27.foo.bar.example.com
>
>the MAIL FROM is null, HELO is mta27.foo.bar.example.com, and the SPF
>record for mta27.foo.bar.com says that IP is OK.

I wish I could type: ... for mta27.foo.bar.example.com says that the IP is OK.

>I don't feel strongly about whether to use the HELO name but it doesn't break anything.

R's,
John