Re: [ietf-smtp] sm8: bogus SMTPUTF8? (was: How is EAI mail implemented ?)

Claus Assmann <ietf-smtp@esmtp.org> Wed, 16 June 2021 18:46 UTC

Return-Path: <ietf-smtp@esmtp.org>
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 7D9F23A2288 for <ietf-smtp@ietfa.amsl.com>; Wed, 16 Jun 2021 11:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 QKjOEfPg12R1 for <ietf-smtp@ietfa.amsl.com>; Wed, 16 Jun 2021 11:46:02 -0700 (PDT)
Received: from kiel.esmtp.org (kiel.esmtp.org [195.244.235.220]) (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 C0DD33A2284 for <ietf-smtp@ietf.org>; Wed, 16 Jun 2021 11:46:02 -0700 (PDT)
Received: from kiel.esmtp.org (localhost. [127.0.0.1]) by kiel.esmtp.org (MeTA1-1.1.Alpha16.0) with ESMTPS (TLS=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256, verify=OK) id S000000000005EE2A00; Wed, 16 Jun 2021 20:45:58 +0200
Received: (from ca@localhost) by kiel.esmtp.org (8.16.0.41/8.12.10.Beta0/Submit) id 15GIjwJ8039778 for ietf-smtp@ietf.org; Wed, 16 Jun 2021 20:45:58 +0200 (CEST)
Date: Wed, 16 Jun 2021 20:45:58 +0200
From: Claus Assmann <ietf-smtp@esmtp.org>
To: ietf-smtp@ietf.org
Message-ID: <20210616184558.GA98351@kiel.esmtp.org>
Reply-To: ietf-smtp@ietf.org
Mail-Followup-To: ietf-smtp@ietf.org
References: <5bb26c2f-a94d-ccaf-8fc1-51684f25f48@taugh.com> <20210615182626.GA57503@kiel.esmtp.org> <50d39b92-77b7-3857-d73c-d6902b6a7ee@taugh.com> <20210616054157.GA49467@kiel.esmtp.org> <sad817$oci$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <sad817$oci$1@gal.iecc.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/qClGIA-o5wC3JXn24GstScfpH20>
Subject: Re: [ietf-smtp] sm8: bogus SMTPUTF8? (was: How is EAI mail implemented ?)
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: Wed, 16 Jun 2021 18:46:08 -0000

On Wed, Jun 16, 2021, John Levine wrote:

> It was locally injected with "sendmail -fuser1@xn--5nq21jyu9d1ta.xn--5nqx41au4nqohsp3axcg.xn--fiqs8s atest@xn--fct.xn--5nqx41au4nqohsp3axcg.xn--fiqs8s"

Do you still have that "shim" (mentioned in a usenet posting)?
  In my tests I worked around it with a one line shim that always adds
  -U to the sendmail command and my guess is that everyone will do that.
Hopefully not -- because currently sendmail doesn't "downgrade",
i.e., it does not check whether SMTPUTF8 could be removed
(maybe this might be implemented in a future version).

-- 
Address is valid for this mailing list only, please do not reply
to it direcly, but to the list.