From 7ded13dafb6a29dcbbbabc32008685db49d42f77 Mon Sep 17 00:00:00 2001 From: Simon Fondrie-Teitler Date: Fri, 29 Sep 2017 12:12:23 -0400 Subject: [bug] Keep content-type when it is set in message headers When content-type was set in the message headers instead of the MIMEPart (e.g. when not using MIMEParts in the message) bitmask would ignore it and add the content as text/plain. This caused problems with Nylas. To fix this, if the message is not Multipart I'm keeping the assumption that everything is going to have the maintype of "text" but copying the subtype from the original message. This also decodes the original message's payload before attaching the old content to the new message to make up for the loss of encoding information. -Resolves: #9064 --- docs/changelog.rst | 1 + 1 file changed, 1 insertion(+) (limited to 'docs') diff --git a/docs/changelog.rst b/docs/changelog.rst index d197eded..99821b44 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -13,6 +13,7 @@ Features Bugfixes ~~~~~~~~ - `#9099 `_: properly check for openvpn binary path in bundles. +- `#9064 `_: keep content-type when it is set in message headers. - Ship cacert.pem inside Bitmask.app - Avoid importing linux-specific constants in firewall helpers. -- cgit v1.2.3