MBOX-Line: From blong at google.com  Wed Oct 16 15:42:49 2013
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun  8 12:34:51 2018
Subject: [Imap-protocol] Accessing the Content-Transfer-Encoding of a
	top-level multipart
In-Reply-To: <27ae442a-80d7-4451-a416-2512d25052f4@email.android.com>
References: <18960e4a-19cb-4a82-b287-aee478965e77@flaska.net>
	<CAKHUCzwE6K_ySgiTuHxXyX2V7z+etTngCQHRcQFzt6mNpSWA8Q@mail.gmail.com>
	<27ae442a-80d7-4451-a416-2512d25052f4@email.android.com>
Message-ID: <CABa8R6vjYgeKKg77O=e-F88UKbCyBG-79WbX1F5jFp16f+pM_g@mail.gmail.com>

Yes, you're allowed non-transformative types... and for more fun, RFC
6532 for message/global so you can have UTF8 headers.

Brandon

On Wed, Oct 16, 2013 at 2:30 PM, Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no> wrote:
> No, multipart does not have a cte at all. The leaf parts may have different
> cte values.
>
> As I recall, there is a ban on sending cte for a multipart somewhere in the
> mime documents.
>
>
> Arnt
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol

