IETF Logo Mail Archive

Re: [ietf-smtp] EHLO domain validation requirement in RFC 5321

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Sun, 04 October 2020 16:59 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C64203A08C1 for <ietf-smtp@ietfa.amsl.com>; Sun, 4 Oct 2020 09:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
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 uq2HMLqVny2m for <ietf-smtp@ietfa.amsl.com>; Sun, 4 Oct 2020 09:59:08 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BAF53A08C0 for <ietf-smtp@ietf.org>; Sun, 4 Oct 2020 09:59:07 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 5FFBEC0175; Sun, 4 Oct 2020 18:05:17 +0100 (IST)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=none smtp.mailfrom=arnt@gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1601831117; bh=+vznr7DjFHGqH6p2SX0oWy/2Cqhe9oZvTysolwN2I8g=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=E0NVa7AfMIuPlJL1Hpi3Xo5lQhvWokb+/A6ET8QXfN4n9WY4Rqrp2CPKD6p3GIiYd QGG+nqIXbhWMP/wZgxPHsX4E4Wcvxhwb0OpfrxzDvXfFKeOFK/sjOw6CSnVWatsVuq 7iarz4SHpuFDLwyr/ZcTa4sGu41zVEaxnHJiMka8=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1601831115-19142-19140/9/242; Sun, 4 Oct 2020 17:05:15 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf-smtp@ietf.org
Date: Sun, 04 Oct 2020 19:13:10 +0200
Mime-Version: 1.0
Message-Id: <1c1856a5-ae46-48a0-84cd-66eafb543fa9@gulbrandsen.priv.no>
In-Reply-To: <a692482a-7777-5743-0820-894dbe7314b0@network-heretics.com>
References: <20200928221602.046CE22A35B3@ary.qy> <ADA8052C-2B7D-4C50-8FFF-A3D88EC3BA58@isc.org> <ab8886ec-79b1-a89c-da38-dfe5a6e681@taugh.com> <a692482a-7777-5743-0820-894dbe7314b0@network-heretics.com>
User-Agent: Trojita/0.7; Qt/5.11.3; xcb; Linux; Devuan GNU/Linux 3 (beowulf)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/tSJiGPGcLmgtCv3fQoM29fs2T_w>
Subject: Re: [ietf-smtp] EHLO domain validation requirement in RFC 5321
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Oct 2020 16:59:11 -0000

On Sunday 4 October 2020 11:49:29 CEST, Keith Moore wrote:
> Please cite these "well established anti-abuse metrics" because 
> they should not be accepted as valid without question.

Actually, a significant set of email senders do question and do not accept 
them, so you're in a lot of company here, even if it may not be very good 
company ;)

But there's another aspect. Who accepts? These things are the content of 
.procmailrc files and sieve scripts. Who has authority to accept or not 
accept the validity of what I write in my sieve script? I believe that's a 
local matter, out of scope for the IETF, and therefore off-topic for all 
IETF lists.

Arnt

v2.23.0 | Report a Bug | By Email