Re: [ietf-smtp] spinning our wheels, was Fwd: New Version Notification for draft-crocker-email-deliveredto-02.txt

Sam Varshavchik <mrsam@courier-mta.com> Tue, 02 March 2021 05:47 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 BBE5E3A1F06 for <ietf-smtp@ietfa.amsl.com>; Mon, 1 Mar 2021 21:47:57 -0800 (PST)
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 nVVhtJK4YXgJ for <ietf-smtp@ietfa.amsl.com>; Mon, 1 Mar 2021 21:47:56 -0800 (PST)
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 612AE3A2002 for <ietf-smtp@ietf.org>; Mon, 1 Mar 2021 21:47:56 -0800 (PST)
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 UTF8SMTPS id 00000000002C04EF.00000000603DD186.000063A5; Tue, 02 Mar 2021 00:47:50 -0500
Received: from monster.email-scan.com (localhost [127.0.0.1]) (IDENT: uid 1004) by monster.email-scan.com with UTF8SMTP id 000000000001E569.00000000603DD185.000112F9; Tue, 02 Mar 2021 00:47:49 -0500
References: <20210221202821.3F43D6E6BC67@ary.qy> <603D86C8.2080406@isdg.net>
Message-ID: <cone.1614664069.629364.70261.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: Tue, 02 Mar 2021 00:47:49 -0500
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=_monster.email-scan.com-70261-1614664069-0002"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/CmoRuJGB5w1EoM8V4JbHvdHgMvw>
Subject: Re: [ietf-smtp] spinning our wheels, was Fwd: New Version Notification for draft-crocker-email-deliveredto-02.txt
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: Tue, 02 Mar 2021 05:47:58 -0000

Hector Santos writes:

> For the record, after 25 years, Wildcat! SMTP (or did Wildcat! UUCP) have  
> never needed, nor considered, nor knew existed nor did we looked the  
> "Delivered-To" header.
>
> What problem does it solve?

One problem in definitely solved was detecting mail loop as soon as it's  
practically possible, without having to wait until a message ping-ponged a  
bunch of times between servers. You still need to count Received: headers,  
but most mail loops get broken right away.

Beyond that, it offered mail handling software a means to avoid the need for  
explicit configuration of their mailbox address. They'll just pick it up  
from the Delivered-To: header, and run with it. This is much easier than  
picking apart the bits of the topmost Received: header, looking for the  
"for", and hoping to find one.