IETF Logo Mail Archive

Re: [ietf-smtp] How is EAI mail implemented ?

John Levine <johnl@taugh.com> Tue, 15 June 2021 23:51 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 F37323A42CE for <ietf-smtp@ietfa.amsl.com>; Tue, 15 Jun 2021 16:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=zZKbX3LI; dkim=pass (2048-bit key) header.d=taugh.com header.b=j5kQ+/SR
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 9qYuPkrYguCr for <ietf-smtp@ietfa.amsl.com>; Tue, 15 Jun 2021 16:51:30 -0700 (PDT)
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 47DAE3A42CC for <ietf-smtp@ietf.org>; Tue, 15 Jun 2021 16:51:30 -0700 (PDT)
Received: (qmail 10810 invoked from network); 15 Jun 2021 23:51:28 -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:cleverness; s=2a37.60c93d00.k2106; bh=9BMqVTrSNQFg42XqLHZc0FX4w1mVEQrNm8kVsI1r4Ig=; b=zZKbX3LI/9zE3VIZQpmdV6oIV7tyt9vkSDHBU/Z/aYTGTDnsBbf2ElM/Y7HI0Q2GZgRvZdyZAScE972EewqQGYeXEUmLpXRkDvI+fEYghKmZ1NkPtOGIOzsafhZhGEdJjvw/IRxOVd29byi7O1bUuRvUaNJZknFpVIMuQ+M+Ukj3SQKctGLK25EVc5Rx74AHugaOFoZvzYfA3QeKsy/j8aV49+coTxFV1k5LSSbdvCWbprIkivN0k+ZA5x5S3eQtZrky5TsCnp7cgGWcRzxBG0iNVyWgzvlZKT/psmPN3dmV9ngs96vLiByXjMNfbb4naZcP9Ne4U6EUtsOBkunM+A==
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:cleverness; s=2a37.60c93d00.k2106; bh=9BMqVTrSNQFg42XqLHZc0FX4w1mVEQrNm8kVsI1r4Ig=; b=j5kQ+/SRLqpLKZHM3uEgnA0izlDmTD/TXXNQi0SqNh89IyAv88OC1hjpVy3aUVRIyLZ7J9dVPTEbzeu/c+kTIk+1b0cvhzSyncmH6OffA0VG4XFlkzFGKMlsCSgbEhJgVi3Z2UTxDnoTVt88HilLKuqz6OfAfHbC6NopiYDsd2lRI2/TWMwtik01BM5xoi2YghTRSCTHvu2C2YXCrfT0NFaXQVYuxLrWNLVVPrdZMblN1oFcBT2+HrlICvDD7NaUN/7SRIqNHEx4mloRJyh9hh269nHDZGinMXfHI/32baUUVyMIWv6wom5g9Z8RDagFOIFWZfaHU/5c8/wG91cD8w==
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 ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 15 Jun 2021 23:51:28 -0000
Received: by ary.qy (Postfix, from userid 501) id 769B31171A6E; Tue, 15 Jun 2021 19:51:27 -0400 (EDT)
Date: Tue, 15 Jun 2021 19:51:27 -0400
Message-Id: <20210615235127.769B31171A6E@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: mrsam@courier-mta.com
In-Reply-To: <cone.1623797013.955385.61687.1004@monster.email-scan.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
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/UdwF82NBofX3J-sTQe7rC63qCrU>
Subject: Re: [ietf-smtp] 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: Tue, 15 Jun 2021 23:51:36 -0000

It appears that Sam Varshavchik  <mrsam@courier-mta.com> said:
>A few months ago someone @icann.org contacted me regarding "UASG030 EAI  
>Testing Results for Courier". After swapping a few messages, the upshot was  
>that, apparently, the testing apparatus that was employed in that endeavor  
>expected SMTPUTF8 senders specify the UTF8 flag on anything that's sent to a  
>receiver that advertises SMTPUTF8, even if it's pure ASCII.

The person running the tests these days is me, and that's the exact
opposite of what the tests are looking for, that it *doesn't* send the
UTF8 flag on ASCII mail. I didn't run the tests on Courier, but I
think the people who did checked correctly.

By the way, last time I checked, when Courier adds a Received line it says
UTF8ESMTP rather than UTF8SMTP.  Did you ever get around to fixing that?  It
looks like a one or two line fix.  Exim had the same bug.

R's,
John

v2.23.0 | Report a Bug | By Email