Re: IETF Policy on dogfood consumption or avoidance - SMTP version

Viktor Dukhovni <ietf-dane@dukhovni.org> Sun, 15 December 2019 23:19 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3D8120013 for <ietf@ietfa.amsl.com>; Sun, 15 Dec 2019 15:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 i56mTMggscMd for <ietf@ietfa.amsl.com>; Sun, 15 Dec 2019 15:19:22 -0800 (PST)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35CFE12000F for <ietf@ietf.org>; Sun, 15 Dec 2019 15:19:22 -0800 (PST)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 61AC24E6B0; Sun, 15 Dec 2019 18:19:21 -0500 (EST)
Date: Sun, 15 Dec 2019 18:19:21 -0500
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: IETF Policy on dogfood consumption or avoidance - SMTP version
Message-ID: <20191215231921.GE11489@straasha.imrryr.org>
Reply-To: ietf@ietf.org
References: <8EE11B75E1F8A7E7105A1573@PSB> <6a0a5f8a-9da6-30e7-f4b9-0b263cda507a@foobar.org> <53c77a3d-15d6-fe69-99f2-2c8f2e35826c@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <53c77a3d-15d6-fe69-99f2-2c8f2e35826c@network-heretics.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UskJcWX2a2O3ELInxj8i8knVHnk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Dec 2019 23:19:23 -0000

On Sun, Dec 15, 2019 at 06:04:59PM -0500, Keith Moore wrote:

> I do not find that this is true in general, and IMO it is not a valid
> working assumption.   There's a tremendous amount of Bad Conventional
> Practice out there, especially in both email handling and security,
> that has come to be accepted as if it were wisdom.

Yes, there is much cargo-culting of questionable practice.  But there
are also in some cases specifications that (no longer) match operational
realities.  Which is not to suggest that support for address literals is
necessarily such an example, it rather depends on metrics I don't have,
and which may even be time and place specific.

Perhaps there was once a particular stream of abuse directed at ietf.org
that the rule in question stopped.  It may still be effective, then and
could now be merely a low-volume source of false-positives.  Or it could
still be, perhaps intermittently, an effective way to distinguish spam
from ham.

If I were the operator of the MTA in question, I'd consider dropping the
rule after checking recent logs for signs of its efficacy.

-- 
    Viktor.