wasm-demo/demo/ermis-f/imap-protocol/cur/1600095014.22623.mbox:2,S

32 lines
1.3 KiB
Plaintext

MBOX-Line: From arnt at gulbrandsen.priv.no Wed Sep 3 23:10:05 2014
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
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: <1409785422.1122.9.camel@16bits.net>
References: <5400A146.4020602@mozilla.com>
<CABa8R6se2WefF4q-cFzR2qtU_5_jDL-wioPF+jPmOTdpCaJhtw@mail.gmail.com>
<54011E24.4080209@mozilla.com>
<6f3e9961-32e6-4b4b-866f-7ce5526b0bf8@gulbrandsen.priv.no>
<CABa8R6vJUAo231ECkLyDsTmk08UGgS2E7i6SNZ==x6YwFOiPUw@mail.gmail.com>
<1409774552.1122.3.camel@16bits.net>
<03710d62-c480-4224-b33a-96f979ebd1a3@gulbrandsen.priv.no>
<1409778099.1122.7.camel@16bits.net>
<ca684549-f7c8-4260-bf34-329ff2671e1c@gulbrandsen.priv.no>
<1409785422.1122.9.camel@16bits.net>
Message-ID: <09c251b8-ba35-476e-a3d2-1e352c0ce58f@gulbrandsen.priv.no>
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