MBOX-Line: From arnt at gulbrandsen.priv.no  Thu Oct 17 01:56:13 2013
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun  8 12:34:51 2018
Subject: [Imap-protocol] Accessing the Content-Transfer-Encoding of a
	top-level multipart
In-Reply-To: <CABa8R6vjYgeKKg77O=e-F88UKbCyBG-79WbX1F5jFp16f+pM_g@mail.gmail.com>
References: <18960e4a-19cb-4a82-b287-aee478965e77@flaska.net>
	<CAKHUCzwE6K_ySgiTuHxXyX2V7z+etTngCQHRcQFzt6mNpSWA8Q@mail.gmail.com>
	<27ae442a-80d7-4451-a416-2512d25052f4@email.android.com>
	<CABa8R6vjYgeKKg77O=e-F88UKbCyBG-79WbX1F5jFp16f+pM_g@mail.gmail.com>
Message-ID: <20131017085613.GB15056@gulbrandsen.priv.no>

On Wed, Oct 16, 2013 at 03:42:49PM -0700, Brandon Long wrote:
> Yes, you're allowed non-transformative types... and for more fun, RFC
> 6532 for message/global so you can have UTF8 headers.

Right. I had forgotten that detail.

Put differently: You're allowed to specify any CTE which is equivalent
to not specifying CTE. I expect that's why Mark didn't want to include
the CTE when reporting header contents.

Arnt

