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

Sam Varshavchik <mrsam@courier-mta.com> Sun, 27 September 2020 13:01 UTC

Return-Path: <mrsam@courier-mta.com>
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 F025B3A0403 for <ietf-smtp@ietfa.amsl.com>; Sun, 27 Sep 2020 06:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 MAdp_tKzyr5F for <ietf-smtp@ietfa.amsl.com>; Sun, 27 Sep 2020 06:01:38 -0700 (PDT)
Received: from mailx.courier-mta.com (mailx.courier-mta.com [68.166.206.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64753A03FB for <ietf-smtp@ietf.org>; Sun, 27 Sep 2020 06:01:37 -0700 (PDT)
Received: from monster.email-scan.com (monster.email-scan.com [::ffff:192.168.0.2]) (TLS: TLSv1.3,256bits,TLS_AES_256_GCM_SHA384) by www.courier-mta.com with UTF8ESMTPS id 00000000002C0020.000000005F708D30.0000311A; Sun, 27 Sep 2020 09:01:36 -0400
Received: from monster.email-scan.com (localhost [127.0.0.1]) (IDENT: uid 1004) by monster.email-scan.com with UTF8SMTP id 000000000001C7C3.000000005F708D30.00006143; Sun, 27 Sep 2020 09:01:36 -0400
References: <cone.1600468578.784468.161845.1004@monster.email-scan.com> <da460777-824b-1f13-be7c-32bfa9664d02@network-heretics.com>
Message-ID: <cone.1601211696.103163.24342.1004@monster.email-scan.com>
X-Mailer: http://www.courier-mta.org/cone/
From: Sam Varshavchik <mrsam@courier-mta.com>
To: ietf-smtp@ietf.org
Date: Sun, 27 Sep 2020 09:01:36 -0400
Mime-Version: 1.0
X-Mime-Autoconverted: from 8bit to quoted-printable by mimegpg
Content-Type: multipart/signed; boundary="=_monster.email-scan.com-24342-1601211696-0002"; micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/L_ETYpSHpveU3-i9VbPtu9xOZSk>
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, 27 Sep 2020 13:01:39 -0000

Keith Moore writes:

> the fact that it works as a spam filter today seems like mere circumstance  
> or accident; I don't see any inherent reason that it will be a reliable spam  
> filter going into the future.   Spammers do learn, if slowly, so if they  
> have to learn to make sure their EHLO arguments match their source IP  
> addresses, they'll do that.   In the long term, I don't think this check  
> helps anything.

Yes, I agree. Domain validation is not mainstream, but it is being use in  
practice, just enough to fall under the radar stream. If for any reason –  
whether explicitly blessed in an RFC or for any other reason – it becomes  
more prevalent then spam generators will certainly adopt.

But at least right now it is a very effective filter. Like I wrote, this is  
really against my self-interest to bring more awareness to it.