IETF Logo Mail Archive

Re: [Extra] IMAP I18NLEVEL

"John Levine" <johnl@taugh.com> Tue, 29 January 2019 02:37 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E344131278 for <extra@ietfa.amsl.com>; Mon, 28 Jan 2019 18:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=cH5T9Xqg; dkim=pass (1536-bit key) header.d=taugh.com header.b=S0HsosPn
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 B6GnnHYn5MfY for <extra@ietfa.amsl.com>; Mon, 28 Jan 2019 18:37:20 -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 915B01312E7 for <extra@ietf.org>; Mon, 28 Jan 2019 18:30:17 -0800 (PST)
Received: (qmail 39531 invoked from network); 29 Jan 2019 02:30:15 -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=9a69.5c4fbab7.k1901; bh=11hsEa31RgU+Q0w3hHNP5kLVUjO/RCkMB9BDiaOJVU4=; b=cH5T9XqgjGVa26uBvyoRAis7vj9YXK4BpMj+ZOdPqLBIXzS7kCxxq4ovm/6MSbrvD8RKkJptPtolZbe7NaxWRlBuTsXEbYmpAbvOEvM05DF3rODgqvgzGW8Z7lEks55YOQrsN+ahMJYnqFISUjQTbRa0Cct6EAXkXi1yKX5IF14/E8ZeZW4FFbzM3FKii5u963lLR0BnCHVVcA/FDJ1wxGsNtcOmNfSvBoWCUg/EQr4O6/NmeS/8mLOo9di116Pp
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=9a69.5c4fbab7.k1901; bh=11hsEa31RgU+Q0w3hHNP5kLVUjO/RCkMB9BDiaOJVU4=; b=S0HsosPnrCTi1VvmOuj5p2k0JNUr8arerx9kuuET2zJJDjtOHRFnSNv4KF/v2IETD2E6R2/ZunpovVQSfnTV5wkt3CBimp8CoOymEnziNOyFS+CYmvddo7ZuuqmvP+fWpf6JXWFhu8wQ8HGjGM/oC9++YnlRkIurBltP6U8Mh0xgnk4VTDBK549ZOPUXBnaUh+SMBjVNlsqXM6TliJIE0ZreFVO3I3fp4ajKPxjgtVEd4eSfJQPscgy70oR8N9qh
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 ESMTP via TCP6; 29 Jan 2019 02:30:14 -0000
Received: by ary.qy (Postfix, from userid 501) id AAC7A200D6AC18; Mon, 28 Jan 2019 21:30:14 -0500 (EST)
Date: Mon, 28 Jan 2019 21:30:14 -0500
Message-Id: <20190129023014.AAC7A200D6AC18@ary.qy>
From: John Levine <johnl@taugh.com>
To: extra@ietf.org
Cc: murch@fastmail.com
In-Reply-To: <923c9a3b-4541-d255-5629-57bfb99e80b3@fastmail.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/extra/B7x8Odv_4B8VBXdvvu0-pxSI0Q4>
Subject: Re: [Extra] IMAP I18NLEVEL
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2019 02:37:23 -0000

In article <923c9a3b-4541-d255-5629-57bfb99e80b3@fastmail.com> you write:
>Some of us at FastMail have been discussing implementing RFC 5255, 
>namely the I18NLEVEL extensions, in the Cyrus IMAP server and we are 
>wondering if any clients support and use them.

Why 5255 rather than RFC 6855?  It is my impression that in practice
the UTF8 support in 6855 made the older stuff obsolete.

Since Chris Newman was an author of both, he's the obvious person to
ask for more info.

v2.23.0 | Report a Bug | By Email