26 lines
1.1 KiB
Plaintext
26 lines
1.1 KiB
Plaintext
MBOX-Line: From arnt at gulbrandsen.priv.no Thu Feb 20 10:02:40 2014
|
|
To: imap-protocol@u.washington.edu
|
|
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
|
Date: Fri Jun 8 12:34:52 2018
|
|
Subject: [Imap-protocol] MUTF7, UTF8, and Unicode flags
|
|
In-Reply-To: <adb5d342-be87-4b56-b4de-8a9ef1f9a243@flaska.net>
|
|
References: <57f94285-8e26-4eb1-9556-826fde4edd89@gulbrandsen.priv.no>
|
|
<adb5d342-be87-4b56-b4de-8a9ef1f9a243@flaska.net>
|
|
Message-ID: <fd58aad8-9a1f-4771-8a6c-ee0535069ff5@gulbrandsen.priv.no>
|
|
|
|
On Thursday, February 20, 2014 6:53:21 PM CEST, Jan Kundr?t wrote:
|
|
> Seriously? This is going to break stuff. You might argue that
|
|
> people creating mailboxes named "&U,BTFw-" are unlikely :), but
|
|
> it's a valid string both in UTF-8 and in the modified UTF-7
|
|
> encoding -- except that the two meanings are very different.
|
|
|
|
Actually, my thinking was (and is) that there's a fighting chance that
|
|
before a new client being written today is ready for production use, UTF8
|
|
might be all you need.
|
|
|
|
Mailboxes named &U,BTw- are not a major concern. An obvious problem, but
|
|
hardly a pressing problem.
|
|
|
|
Arnt
|
|
|