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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14060
------------------------------------------------------------------------------
  Ticket             | 14060
  Updated By         | Git Commit <commits at lists.horde.org>
  Summary            | forwarding messages in the smartmobile view breaks mime
                     | boundaries and encoding
  Queue              | IMP
  Version            | 6.2.9
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Michael Rubinsky
------------------------------------------------------------------------------


Git Commit <commits at lists.horde.org> (2017-10-20 20:33) wrote:

Changes have been made in Git (FRAMEWORK_5_2):

commit 2b7c9349563f7f4048179a027a8ccd083d51df54
Author: Michael J Rubinsky <mrubinsk at horde.org>
Date:   Mon, 28 Nov 2016 13:17:12 -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.

  M lib/Compose.php

https://github.com/horde/imp/commit/2b7c9349563f7f4048179a027a8ccd083d51df54