wasm-demo/demo/ermis-f/imap-protocol/cur/1600095020.22659.mbox:2,S

20 lines
934 B
Plaintext

MBOX-Line: From arnt at gulbrandsen.priv.no Wed Oct 16 14:30:15 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: <CAKHUCzwE6K_ySgiTuHxXyX2V7z+etTngCQHRcQFzt6mNpSWA8Q@mail.gmail.com>
References: <18960e4a-19cb-4a82-b287-aee478965e77@flaska.net>
<CAKHUCzwE6K_ySgiTuHxXyX2V7z+etTngCQHRcQFzt6mNpSWA8Q@mail.gmail.com>
Message-ID: <27ae442a-80d7-4451-a416-2512d25052f4@email.android.com>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20131016/ba4a2e09/attachment.html>