Tickets :: Comment on [#14060] forwarding messages in the smartmobile view breaks mime boundaries and encoding

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .___.___.__ \|_/ [__)[__ [__ [__) \| \[__)\| \| \| \
Comment	> Changes have been made in Git (FRAMEWORK_5_2): > > commit 8c2478ebb8a230aa0206908fcd75f8e3ce842286 > Author: Michael J Rubinsky <mrubinsk@horde.org> > Date: Mon Nov 28 13:08:48 2016 -0500 > > Bug: 14060 Fix various Content-Type header issues when forwarding email. > > In mobile view when forwarding (and maybe when sending any message > with attachments in any view) to multiple recipeients, and choosing > any encryption option (even if the email ends up not being encrypted) > - this causes multiple MIME objects to be generated (one for each > recipient), > however the header object for the base part was being reused, > thus causing > issues with things like MIME part boundries and charsets etc...Was an > issue in mobile view because of the way the original message is added as > an attachment during the message building. > > Looks like this entire section of code was refactored in git master in > such a way that this fix is not necessary there. > > imp/lib/Compose.php \| 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > > http://github.com/horde/horde/commit/8c2478ebb8a230aa0206908fcd75f8e3ce842286
Attachment
Watch this ticket