[Tickets #14060] Re: forwarding messages in the smartmobile view breaks mime boundaries and encoding
noreply at bugs.horde.org
noreply at bugs.horde.org
Mon Nov 28 18:19:10 UTC 2016
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 | Assigned
Priority | 1. Low
Milestone |
Patch |
Owners | Horde Developers
------------------------------------------------------------------------------
Git Commit <commits at lists.horde.org> (2016-11-28 18:19) wrote:
Changes have been made in Git (FRAMEWORK_5_2):
commit 8c2478ebb8a230aa0206908fcd75f8e3ce842286
Author: Michael J Rubinsky <mrubinsk at 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
More information about the bugs
mailing list