MBOX-Line: From tss at iki.fi  Sat Oct 27 17:23:49 2007
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:40 2018
Subject: [Imap-protocol] re: GMail
In-Reply-To: <alpine.OSX.0.9999.0710271708460.11181@pangtzu.panda.com>
References: <alpine.WNT.0.9999.0710241938220.520@Shimo-Tomobiki.Panda.COM>
	<fc2c80ae0710270911o23f0b366g942b2956ac3fa@mail.gmail.com>
	<alpine.WNT.0.9999.0710270924180.4788@Shimo-Tomobiki.Panda.COM>
	<5202.1193523708.069559@peirce.dave.cridland.net>
	<alpine.OSX.0.9999.0710271708460.11181@pangtzu.panda.com>
Message-ID: <1193531029.25921.561.camel@hurina>

On Sat, 2007-10-27 at 17:10 -0700, Mark Crispin wrote:
> On Sat, 27 Oct 2007, Dave Cridland wrote:
> > But I'd like to turn off all the legacy encoding at the same time. Mailboxes, 
> > keywords, headers, bodies - the lot.
> 
> You mean that you want the server to translate charsets to UTF-8?  I would 
> support doing that with an alternative form of FETCH, e.g., UTF8.FETCH. 
> But then there would have to be an error on a charset conversion failure, 
> and it begs the question as to why the CONVERT extension in Lemonade 
> doesn't do that.

Converting message bodies would break cryptographic signatures.
Converting headers automatically might also do bad things. I guess
ENVELOPE, BODY and BODYSTRUCTURE could be returned converted, but I
don't know if that helps much.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20071028/ffd8fe73/attachment.sig>
