2. Content-Transfer-Encoding: 7bit
The 2nd is more of a property assertion, than an encoding. The
MIME-part content is transmitted as-is, but is asserted to consist
entirely of 7-bit octets (i.e. still 8-bit octets, but in the range
0–127). Similarly, the "8bit" transfer encoding is also an "identity"
encoding, which makes no promise about the high bit of the content.
(1) With testing (sent from roundcube, read from gmail) I found that:
X-Sender: t...@myposts.ovh
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
两鬓可怜青，只为相思老。
无情不似多情苦，一寸还成千万缕。
As you see with chinese UTF8 characters the transfer-encoding has been
set to 8bit.
(2) When I sent the message with an image, the header shows:
Content-Transfer-Encoding: base64
Content-ID: <1680959471643167ef91cbd862656...@myposts.ovh>
Content-Type: image/jpeg; name=17ED2A46-3D73-4E4B-82A9-AECD793906CC.jpeg
As you see now transfer-encoding becomes base64.
So my guess:
(1) in smtp session, both 7bit, 8bit are allowed. for example, UTF-8 use
8bit for transfer.
(2) If the content is binary, base64 or QP should be used. in transfer
process, base64 still uses 7bit.
Am I right?
Thank you.
Tom.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
