Can someone update cvs branches as well? HEAD,FRAMEWORK and probably 
groupwares
thanks.

I've changed it to:
         return base_convert(dechex(strtr(microtime(), array('0.' => 
'', ' ' => ''))) . uniqid(mt_rand(), true), 16, 36);

in git.

I found the problem.
It comes from MIME::generateRandomID(). The random ID generated is not 
uniq. When you call this function several time within a sort period of 
time, you always get the same random ID.

quick fix which works here :
     function generateRandomID()
     {
//        return base_convert(dechex(strtr(microtime(), array('0.' => 
'', ' ' => ''))) . uniqid(), 16, 36);
         return md5(microtime());
     }

hope this helps.

So long as the same problem doesn't happen with that code...

IMP 5/new MIME library is less than a week away from being stable 
enough to replace the current CVS HEAD code, so I am not going to look 
at this.  If someone else wants to, they are more than welcome.

I can confirm the problem.

Possible patch.
It solves the bug we're having.
but the patch creates an other problem : it does add 2 ending boundary 
at the end of the email.

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 ?

Sorry,
I can't see the attachment in IMP.

And what _is_ the problem?

using the latest CVS version, compose editor is FCKEditor.

How to reproduce :
compose a new email, add text, add an attachment. and send it.

I've attached a copy of the email that has been sent.

I'm not familiar with boundaries, but it seems that the ending 
boundary is added just before the attachment.

I have a CVS copy of horde/IMP from the 07/10/2008, and it was working.