Re: [PATCH] multipart MIME output

Here you go:


On Jul 01, 2008, at 18:27, Stipe Tolj wrote:

> P. A. Bagyenda schrieb:
>> Stipe,
>> I did that test before sending the patch. Basically that test is  
>> broken because the multipart-msg.txt is not strictly speaking a  
>> well-formed multipart/mime message. In particular, some message  
>> headers are terminated by CR instead of CRLF. This is why I  
>> attached a new multipart-msg.txt, which is MIME conformant. On that  
>> one we pass with flying colours.  (I guess I should have made a  
>> patch!)
>> Note of course that mime.[ch] is forgiving of improperly  
>> constructed MIME such as the above when parsing. It does however  
>> generate correct MIME on the output side. Hence the discrepancy.
>
> ok, understand. Can you post the "new" multipart-msg.txt as  
> attachement, so we can confirm the patched test program runs as  
> expected? So I can commit the changes to CVS.
>
> Stipe
>
> -------------------------------------------------------------------
> Kölner Landstrasse 419
> 40589 Düsseldorf, NRW, Germany
>
> tolj.org system architecture      Kannel Software Foundation (KSF)
> http://www.tolj.org/              http://www.kannel.org/
>
> mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
> -------------------------------------------------------------------

Content-Type: multipart/related; start=<AAA>; boundary=my_boundary
X-Some-Header: Some-Value
MIME-Version: 1.0


--my_boundary
Content-Type: text/plain

this is the text in this entity

--my_boundary
Content-Type: multipart/mixed; boundary=mms_boundary
MIME-Version: 1.0


--mms_boundary
Content-Type: text/plain

this is the mms message text

--mms_boundary
Content-Type: application/xml

<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.0//EN"
  "http://www.wapforum.org/DTD/pap_2.0.dtd">
<pap>
  <push-message push-id="4879683648">
    <address address-value="[email protected]"/>
    <address address-value="[email protected]"/>
    <address address-value="[email protected]"/>
  </push-message>
</pap>

--mms_boundary--

--my_boundary--