Re: [ietf-smtp] DSNs

Scott Kitterman <sklist@kitterman.com> Sun, 26 April 2020 21:59 UTC

Return-Path: <sklist@kitterman.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 BEBBD3A1396 for <ietf-smtp@ietfa.amsl.com>; Sun, 26 Apr 2020 14:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=f6JL9A7a; dkim=pass (2048-bit key) header.d=kitterman.com header.b=PGFbCGg4
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 A2klgd_Nyt8b for <ietf-smtp@ietfa.amsl.com>; Sun, 26 Apr 2020 14:59:20 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523673A1394 for <ietf-smtp@ietf.org>; Sun, 26 Apr 2020 14:59:20 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 8FD3BF8020E for <ietf-smtp@ietf.org>; Sun, 26 Apr 2020 17:59:18 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1587938358; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=N203bUX28l1KzklGkdiGKh0JluQre5bRHd7hYE9s2Qw=; b=f6JL9A7a2q/A95CUi2bxUGgAeRtjnXw9ZaXRMrY5Cz2O1kcz0ACR4hVYiDzr5D6uWh2E1 XxuMMso9DnE4HoMAQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1587938358; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=N203bUX28l1KzklGkdiGKh0JluQre5bRHd7hYE9s2Qw=; b=PGFbCGg43EuCOcEnnk9YqY9Rsr+q09aNGYC3VPFzTxNNtw+rzNlxIdxlD/nMDx3yscY+7 c0TDyJiHJdQiS1RIrrp3SYacs+x16Fpf0OR1bmcjL6aFN0A+/sHSFE0x8uVkJFcGdFVQjo3 AceYvTpt6SkCwaTgNuZ2rOG9LUAy+tDzJtqL6nsXTNCbES6Tog+w7C/8prwuuVcWHvCdgx1 uLoMC6T/Po1gunvZehNRoFJbNjb/YBQ5Wz0T9PrGrubpt/dAsMOc46+yWrvGk1RSFTH4/KK qOTW6wk4uLJzJHEk749zkSu4TAkNoeK+Ar7BBXcNLUMRhvbKnkDq5+JczAnw==
Received: from sk-desktop.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 5AAF0F800E7 for <ietf-smtp@ietf.org>; Sun, 26 Apr 2020 17:59:18 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: ietf-smtp@ietf.org
Date: Sun, 26 Apr 2020 17:59:18 -0400
Message-ID: <18283689.H6AGmmZv0G@sk-desktop>
In-Reply-To: <147574.1587938016@turing-police>
References: <20200409230011.F039B17637D0@ary.qy> <01RK5UDUPC5W000058@mauve.mrochek.com> <147574.1587938016@turing-police>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/gW05sA7q8gC7aU9FkDr2Yne_zIQ>
Subject: Re: [ietf-smtp] DSNs
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, 26 Apr 2020 21:59:22 -0000

On Sunday, April 26, 2020 5:53:36 PM EDT Valdis Klētnieks wrote:
> On Sun, 26 Apr 2020 11:26:09 -0700, Ned Freed said:
> > All this 10,000 feet stuff is starting to make my head spin. Let's please
> > focus on the specific issue that's been identified here, which is that
> > sites are turning off the DSN extension entirely on ingress systems
> > because
> > they believe they have to in order to comply with the specification.
> 
> The other big problem is that even if we chunk out an RFC that clarifies
> that they *can* pick-and-choose which DSN events to react to on a case by
> case basis, it's still going to take a decade before people actually do
> something about it.

I think that's backwards.  People already have done something about it and do 
pick and choose.  The question is if and how we should align standards to that 
reality.

We could pick the not unusual for the IETF path of defining a third path which 
makes everyone wrong (the new reply code suggestion comes to mind), but I 
think that for this topic if we are going to make a change, it should be to 
align standards to reality rather than attempt the reverse.

Scott K