MBOX-Line: From tss at iki.fi  Sat Oct 27 16:10:23 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: <5202.1193523708.069559@peirce.dave.cridland.net>
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>
Message-ID: <1193526623.25921.536.camel@hurina>

On Sat, 2007-10-27 at 23:21 +0100, Dave Cridland wrote:
> > MUTF7 sucks.  We all know that.  We should move forward on IMAP  
> > UTF-8 ASAP.  I think that we should have a sweet, short, RFC in  
> > which a server advertises a UTF8 capability which the client has to  
> > switch on.  When on, the server accepts and outputs UTF-8 instead  
> > of MUTF7.  It is up to server how the strings are stored  
> > internally, but if it stored in UTF-8 then it must convert to/from  
> > MUTF7 when not in UTF-8 mode.
> 
> +1 - I was just having this conversation with - apparently - the same  
> person you were.
> 
> But I'd like to turn off all the legacy encoding at the same time.  
> Mailboxes, keywords, headers, bodies - the lot.

What do you mean by header/body legacy encoding?

-------------- 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/4ad00f02/attachment.sig>
