6.0.0-beta1
7/20/25

[#12040] mime boundary incorrect in sent message copy after replying
Summary mime boundary incorrect in sent message copy after replying
Queue Synchronization
Queue Version Git master
Type Bug
State Resolved
Priority 2. Medium
Owners mrubinsk (at) horde (dot) org
Requester horde (at) tomseeley (dot) co (dot) uk
Created 02/13/2013 (4540 days ago)
Due
Updated 02/15/2013 (4538 days ago)
Assigned 02/14/2013 (4539 days ago)
Resolved 02/15/2013 (4538 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
02/15/2013 11:32:43 PM Michael Rubinsky Comment #5
State ⇒ Resolved
Reply to this comment
Core 2.2.1
02/15/2013 11:32:12 PM Git Commit Comment #4 Reply to this comment
Changes have been made in Git (master):

commit 297f82a27cee597a90ac7b06a6243c2749aa401e
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Fri Feb 15 18:29:57 2013 -0500

     Ensure the MIME headers are present in $copy

     Fixes Bug: 12040

  .../Core/lib/Horde/Core/ActiveSync/Driver.php      |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

http://git.horde.org/horde-git/-/commit/297f82a27cee597a90ac7b06a6243c2749aa401e
02/14/2013 04:26:30 PM Michael Rubinsky Comment #3
Assigned to Michael Rubinsky
Summary ⇒ mime boundary incorrect in sent message copy after replying
State ⇒ Assigned
Reply to this comment
Actually, looks like the Content-Type header is completely missing.
02/13/2013 04:51:57 PM horde (at) tomseeley (dot) co (dot) uk Comment #2 Reply to this comment
Please note I say replying to gmail because that is what I tested, I 
don't actually have any other email account to test from.
02/13/2013 04:39:58 PM horde (at) tomseeley (dot) co (dot) uk Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ mime boundary incorrect when replying to gmail
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ No
New Attachment: broken email again.txt Download
State ⇒ Unconfirmed
Reply to this comment
Platform: horde webmail 5.0.4
AS client: samsung galaxy S2 (4.0.4)

When replying to an externally composed email (gmail) the item stored 
in the users "sent" folder has incorrect mime boundarys.  Specifically 
it declares the boundary to be one thing, but then actually uses 
something else.  This renders the email unreadable in IMP when viewing 
the sent item.

NB. the actual email that arrives at gmail is not corrupt.  When 
viewed on gmail the boundary declaration matches the actual boundary.

Saved Queries