Re: [ietf-smtp] Possible cont4ibution to moving forward with RFC5321bis SMTP

"John Levine" <johnl@taugh.com> Thu, 02 January 2020 22:17 UTC

Return-Path: <johnl@iecc.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 561F412004D for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 14:17:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=ODr/yKjL; dkim=pass (1536-bit key) header.d=taugh.com header.b=eE2Fts0a
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 xcwckm_lhSqs for <ietf-smtp@ietfa.amsl.com>; Thu, 2 Jan 2020 14:17:26 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC6E6120024 for <ietf-smtp@ietf.org>; Thu, 2 Jan 2020 14:17:26 -0800 (PST)
Received: (qmail 83416 invoked from network); 2 Jan 2020 22:17:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=145d5.5e0e6bf5.k2001; i=printer-iecc.com@submit.iecc.com; bh=7jN9Lao5Bq1IC0q3Y44zsiW/WrNokNm0BzQc+OxwvOI=; b=ODr/yKjL+SunESULPXsWYtLlQzL0zGXP6ErBqC8pmteVvvsIMNs/ftZvWkRjNL5qg2ikee9lM8g3Jm0EO2HsZKEbKkRF19PfgSgAgAsyvHDxZszSdiBvFWPuZXivcDgvfMm+Pk53yK8Fp0wtln7Zx4kqf3Q4cWQ5vAYQ7Zb/cM0P+W60THrepUnMY3CyTKaGxYtwFr8d2ZygDQ6xMxW30t2eQsc+dapxkgRU+R/PBDuf7c1ng+J4VScDkStqJ9xf
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=145d5.5e0e6bf5.k2001; olt=printer-iecc.com@submit.iecc.com; bh=7jN9Lao5Bq1IC0q3Y44zsiW/WrNokNm0BzQc+OxwvOI=; b=eE2Fts0agdXW6HatZbe7pz+s9pwT5pcaQen2LQPd606fLQJ//3mvuqOjInwOHOyVXTrW+w+CgqXQ/+BQ87vGSZLYmxzbm7K8YidcokbhQkZA0plZ66aMRcKX1QksXNjeRvW6CP3LfZeC10f0zEMuE2za/q1EMxjiBBCt/Rxm/mZJl9X1Yvj9jOOPB9hTBqrNN4IHhLiplmwt33oDo+K6FAXddlNFGDSQKDtz8Rnh0pgXxLXPtNSLgbY6K183amg7
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 02 Jan 2020 22:17:25 -0000
Received: by ary.qy (Postfix, from userid 501) id 01B3811EB77B; Thu, 2 Jan 2020 17:17:24 -0500 (EST)
Date: Thu, 02 Jan 2020 17:17:24 -0500
Message-Id: <20200102221725.01B3811EB77B@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: moore@network-heretics.com
In-Reply-To: <eaf66404-0060-4363-d5cf-a7d4e2e8160b@network-heretics.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/khgVXlJZ94RcEoO3zeSWqWEMcDg>
Subject: Re: [ietf-smtp] Possible cont4ibution to moving forward with RFC5321bis SMTP
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: Thu, 02 Jan 2020 22:17:28 -0000

In article <eaf66404-0060-4363-d5cf-a7d4e2e8160b@network-heretics.com> you write:
>Good luck trying to get everyone to use these or any other terms, in 
>exactly the way you want them to use them, on any particular occasion.

The people I know don't have any trouble understanding that the same system, and
sometimes the same program, is an MSA when it's talking to an internal submission
client, and an MTA when it's talking to another MTA found using an MX.

You might want to reread RFC 5598 so you use the terms consistently
with the way everyone else does.

R's,
John