[imp] Imp - MIME boundary - missing

[wsopko@mts.net]

I'm having a problem when IMP sends an email with one or more  
attachments. It appears that the mime boundary identifier is missing  
from the message, thus any email program (including IMP) is not able  
to display the message when it is received by the recipient.

I'm using:
Horde 3.1.3
IMP 4.1.3
PHP 4.4.4

The wierd part is the MIME boundary in the email in my sent-mail  
folder is correctly formatted - i.e. I can view the attachment and  
message text in IMP when viewing the sent message in sent-mail.  
However the email that is received by the recipient is missing the  
MIME boundary= part.

Here is an exerpt of the message source of the email in my sent-mail  
(which displays the attachment and body correctly):

Subject: test
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="=_3m1j33l9ocg0"
Content-Transfer-Encoding: 7bit

This message is in MIME format.

--=_3m1j33l9ocg0
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


test body


--=_3m1j33l9ocg0
Content-Type: text/plain;
charset=ISO-8859-1;
name="test.txt"
Content-Disposition: attachment;
filename="test.txt"
Content-Transfer-Encoding: 7bit

test
--=_3m1j33l9ocg0--



Here is the same email as above that was delivered to the mail  
recipient (the message body or attachment is not displayed when  
message is viewed in Imp or Thunderbird):

Subject: test
MIME-Version: 1.0
Content-Type: multipart/mixed;
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)

This message is in MIME format.

--=_3m1j33l9ocg0
Content-Type: text/plain;
charset=ISO-8859-1;
DelSp="Yes";
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


test body


--=_3m1j33l9ocg0
Content-Type: text/plain;
charset=ISO-8859-1;
name="test.txt"
Content-Disposition: attachment;
filename="test.txt"
Content-Transfer-Encoding: 7bit

test
--=_3m1j33l9ocg0--

-------


The only difference between the two are the boundary="=_3m1j33l9ocg0" is missing and there is an extra "-------" at the end.

Any ideas why these parts are different and casuing the delievered  
message to be displayed incorrectly?

Thanks,

Wayne Sopko
wsopko at mts.net