IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Sat, 30 January 2021 21: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 A631E3A117D for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:23:42 -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=QuqSi+QG; dkim=pass (2048-bit key) header.d=taugh.com header.b=ybyAyKXA
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 1Bwo9-JINIJR for <dmarc@ietfa.amsl.com>; Sat, 30 Jan 2021 13:23:41 -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 E08F83A117C for <dmarc@ietf.org>; Sat, 30 Jan 2021 13:23:40 -0800 (PST)
Received: (qmail 1546 invoked from network); 30 Jan 2021 21:23:40 -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:cleverness; s=608.6015ce5c.k2101; bh=oGZoMQV0zwaHZ4tXQYNG6uJiiqT52tULN2m8LLmwA9A=; b=QuqSi+QGXNdgIeY5HZOMbrHDRAMXiptP2Xx0TVqHEkLCVC/sHpRnCgqH0X6hxoju9RMp8ym//xo/j6yJIz/LYu4ZUR2j7YiFWBPyGofF/MEUHz3CT7JToXN32TGz/uWa/V74Fgf31l7EPe/ngvURqMc5sGCZhFI8fTzfKUWez8xHLPzV20PeEif13YSZGktsNS2VdtTEjEEF0At37ONnbS5XR7+ldcQZH5kRwyxlkrC474FT14AWzGOYpzEd5QzyKSOofF7pLUAgTrxAAONRqmmcudbw5bfP1+pjdq9Yn949qqvUncX4S5qa0DfMTOdbulYdY1SkmjG3rHGkAlPpfQ==
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:cleverness; s=608.6015ce5c.k2101; bh=oGZoMQV0zwaHZ4tXQYNG6uJiiqT52tULN2m8LLmwA9A=; b=ybyAyKXA/Jljr6V2OXWA3+CusuooOnwxJhPZF4InokCFZeIce3m0I6s4qbNDUDcRJ+r0Rm8pVcd/+lVQ3FaegTYKDGaIh8n6pg+w3xTzn5I4p9zS3IYmOq6xW/+UuBaEzc6j0QtoP2hg3r0HHGt92s660ozXUqHxE87YtLTM89Gy4BBU31DNRvL8HuGjUdWzQCg9ryZNTYtrrSPty6f9adsCqQiB5PFgnlJMcjVnyrwkUAu8csV/EKO2bVfJYmHAGe7ALHA9Ww77fZH8gsgCuznRESALTgeE8lz2HAqOkDNqa3foeLzqab1aS0tvFpJMTHCsOC6T3za+m+L/cV6TKQ==
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:23:39 -0000
Received: by ary.qy (Postfix, from userid 501) id 447316D04763; Sat, 30 Jan 2021 16:23:38 -0500 (EST)
Date: Sat, 30 Jan 2021 16:23:38 -0500
Message-Id: <20210130212339.447316D04763@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: fenton@bluepopcorn.net
In-Reply-To: <CF0B307A-C83A-4FF9-BC03-9DE28362DF3A@bluepopcorn.net>
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/wdFAd8xT0tvwYWzT__BBXZUjFfA>
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:23:43 -0000

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 don't feel strongly about whether to use the HELO name but it doesn't break anything.

R's,
John

v2.23.0 | Report a Bug | By Email