MBOX-Line: From tss at iki.fi  Tue Jun 24 07:11:08 2008
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:42 2018
Subject: [Imap-protocol] rfc 2231
In-Reply-To: <1726241373.36641214316071101.JavaMail.root@dogfood.zimbra.com>
References: <1726241373.36641214316071101.JavaMail.root@dogfood.zimbra.com>
Message-ID: <1214316668.3904.1831.camel@hurina>

On Tue, 2008-06-24 at 07:01 -0700, Dan Karp wrote:
> > Do other IMAP servers implement RFC 2231 support for
> > BODY/BODYSTRUCTURE?
> > It's been in my TODO for 5 years and today was the first time anyone
> > asked about it. Is it even a good idea to implement it, or why wasn't
> > it included in RFC 3501?
> 
> Yeah, Zimbra does.  The main impetus is the growing number of Mac mail
> clients out there.  They're the only ones that really exercise it,
> though we've also been seeing 2231 headers from some versions of
> Thunderbird.  (One Thunderbird build even does 2231 headers with out-
> of-order continuations, which was a pain in the ass to handle.)

I went and implemented it now myself too. The specification wasn't too
clear as to how the merging was supposed to be done, but I guess with
the test case (worst I could think of):

key*2=ba%; key2*0=a; key3*0*=us-ascii'en'xyz;
 key*0="foo"; key2*1*=b%25; key3*1=plop%; key*1=baz

the results should be:

 key = foobazba%
 key2* = ''ab%25
 key3* = us-ascii'en'xyzplop%25

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