MBOX-Line: From angel at 16bits.net Thu Sep 11 16:02:35 2014 To: imap-protocol@u.washington.edu From: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= Date: Fri Jun 8 12:34:53 2018 Subject: [Imap-protocol] Seeking clarity on Gmail "Access for less secure apps" setting for non XOAuth2 access In-Reply-To: <09c251b8-ba35-476e-a3d2-1e352c0ce58f@gulbrandsen.priv.no> References: <5400A146.4020602@mozilla.com> <54011E24.4080209@mozilla.com> <6f3e9961-32e6-4b4b-866f-7ce5526b0bf8@gulbrandsen.priv.no> <1409774552.1122.3.camel@16bits.net> <03710d62-c480-4224-b33a-96f979ebd1a3@gulbrandsen.priv.no> <1409778099.1122.7.camel@16bits.net> <1409785422.1122.9.camel@16bits.net> <09c251b8-ba35-476e-a3d2-1e352c0ce58f@gulbrandsen.priv.no> Message-ID: <1410476555.2441.1.camel@16bits.net> Arnt Gulbrandsen wrote: > The problem is: What it do if there's a problem, the description includes > UTF8, and the client hasn't indicated via ENABLE that it can handle UTF in > human-readable text. > > The revised problem is: What it do if there's a problem, the description > includes UTF8, and the client hasn't indicated via LANGUAGE that it can > handle UTF in human-readable text. > > Not much difference. > > Arnt You would have several sets of messages for the different languages. Amongst them you include one that is used as default (if no language is sent) and doesn't contain utf-8 characters. Just like LANG=C is limited to ascii.