[Tickets #7671] Re: Problem with Compose and attachment

bugs at horde.org bugs at horde.org
Fri Nov 14 10:53:45 UTC 2008


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

Ticket URL: http://bugs.horde.org/ticket/7671
------------------------------------------------------------------------------
  Ticket             | 7671
  Updated By         | rsalmon at mbpgroup.com
  Summary            | Problem with Compose and attachment
  Queue              | IMP
  Version            | HEAD
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


rsalmon at mbpgroup.com (2008-11-14 05:53) wrote:

I've added a debug line to imp/lib/Compose.php
--- Compose.php.orig	2008-11-14 11:31:45.000000000 +0100
+++ Compose.php	2008-11-14 11:35:20.000000000 +0100
@@ -856,6 +856,7 @@
                  }
              }

+			Horde::logMessage(print_r($mime_message,true), __FILE__, __LINE__,  
PEAR_LOG_ERR);
              /* Add the body text to the message string. */

which gives me the following parts of the email :
     [_type] => multipart
     [_subtype] => mixed
           [_parts] => Array
                 (
                     [1] => MIME_Part Object
                         (
                             [_type] => multipart
                             [_subtype] => mixed
                             [_parts] => Array
                                 (
                                     [1] => MIME_Part Object
                                         (
                                             [_type] => multipart
                                             [_subtype] => alternative
                                             [_parts] => Array
                                                 (
                                                     [1] => MIME_Part Object
                                                         (
                                                             [_type] => text
                                                              
[_subtype] => plain
                                                     [2] => MIME_Part Object
                                                         (
                                                             [_type] => text
                                                             [_subtype] => html
                                     [2] => MIME_Part Object
                                         (
                                             [_type] => image
                                             [_subtype] => jpeg



I'm guessing the problem is coming from function MIME_Part:::toString.
when toString is called : part 1.1 (so part 1.1.1 and  1.1.2)  are  
processed and then an ending boundary is added for the first time.  
then part 1.2 is processed and an ending boundary is added for the  
second time.

Is this correct ?






More information about the bugs mailing list