[imp] IMP4.0rc3 - CID/MIME Multipart Messages

[Brandon Knitter]

[updated subject to reflect correct imp version, horde3 rc3 implied]

Yo all,

I've messed with this, and messed with this...UGH!!   I even tried to decode
what it's problem was by going through all the IMP and Horde framework code.
Man, my head hurts, that's just way complex for me tonite.

I've even read over RFC 2387 a couple times:

     ftp://ftp.ietf.org/rfc/rfc2387.txt

This has even been quite a bit of help in my quest to get this working 
properly:

     http://www.dsv.su.se/~jpalme/ietf/mhtml.html

If you have an example message source which I could look over, which 
allows for
a html attachment to open with img src's pointing to cid:<content-id> internal
MIME parts, that would be awesome.

I'm changed to the multipart/related overall mime type as well, still no luck.
I've messaged with content-disposition settings (every combination of inline
and attachement).

For the record, these look fine in Outlook, so I know I'm close.  I'm sure M$
isn't following the same [public] spec you guys are though! ;-)

Thanks for the help, I'm going to bed!! :)

-- 
-bk





Quoting Brandon Knitter <knitterb at blandsite.org>:

> Fixed that, and I'm still getting the same problem.
>
> The new URL of the example email is at:
>
>      http://home.blandsite.org/~knitterb/horde/imp-example.txt
>
> Horde3 RC3
> IMP 4.0 RC3
>
> The content/type now says:
>
>      ------=_Part_1_1825624.1102404276387
>      Content-Type: image/jpeg; name=img_0
>      Content-Transfer-Encoding: base64
>      Content-ID: img_0
>      Content-Disposition: attachment; filename=img_0
>
> Any clue what's going on?
>
> -- -bk
>
>
>
>
>
> Quoting Michael M Slusarz <slusarz at mail.curecanti.org>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>> Zitat von Brandon Knitter <knitterb at blandsite.org>:
>>>
>>>> I have an example message posted at:
>>>>
>>>>     http://home.blandsite.org/~knitterb/imp-example.txt
>>>>
>>>> In this example, when viewed in IMP 4.0 rc2 I get a number of 
>>>> attachments listed as:
>>>>
>>>>     Part(s):
>>>>     1  unnamed  [text/html]  8.82 KB
>>>>     2  unnamed  [application/octet-stream]  29 KB
>>>>     3  report.pdf  [application/octet-stream] 30 KB
>>>>     3  report.pdf  View as application/pdf  30 KB
>>>>
>>>> When there is actually the text/html attachment, followed by an 
>>>> image with a
>>>> content-id "img_0", followed by a pdf attachment.
>>>>
>>>> In older IMP's this appears as two attachments (as opposed to 4) 
>>>> with one as a
>>>> text/html and the second as a pdf.
>>>
>>> This is still the case, look at the part numbers.
>>>
>>>> The other thing is that when viewing the html attachment, old IMP's would
>>>> properly resolve the "<img src="cid:...">"  to grab the image from 
>>>> the original
>>>> message.  Now it appears that no resolution of the CID is done.
>>>>
>>>> Is that a config option (for either of those)?
>>>
>>> No. Michael can explain this better, but I guess this happens because the
>>> image doesn't have an image/* mime type.
>>
>> Jan is correct.  The image is actually labeled as an 
>> application/octet-stream
>> part so IMP tries not to force viewing of that image.
>>
>> michael
>>
>> _______________________________________
>> Michael Slusarz [slusarz at curecanti.org]
>> -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>>
>>
>>
>>
>>
>
>
> -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>
> !DSPAM:41b55d04294396847128629!
>
>
>