Hello all,
Some brainstorming:
In order for Thunderbird and Evolution to display inline images that are
referred to in a 'cid' URL, I need to bracket the body and the images with
Content-Type: multipart/related, and I need to print a Content-ID header which
is not an issue. If an email contains only a body and some cid images, Exchange
gives me the expected multipart/related header and everything is fine.
However, when an email contains an inline image, for example a company logo in
a signature, and a regular attachment, for example a pdf file, I get the
following:
Content-Type: multipart/mixed; boundary="--part1"
----part1
Content-Type: text/plain
blah blah
<img src="cid:123@abc">
----part1
Content-Type: image/jpeg
Content-ID: <1...@abc>
7651djfgarty893475789
----part1
Content-Type: application/pdf
846578962ergfjksdghfv346bv
----part1--
What Thunderbird would need should look like this:
Content-Type: multipart/mixed; boundary="--part1"
----part1
Content-Type: multipart/related; boundary="--part1A"
----part1A
Content-Type: text/plain
blah blah
<img src="cid:123@abc">
----part1A
Content-Type: image/jpeg
Content-ID: <1...@abc>
7651djfgarty893475789
----part1A--
----part1
Content-Type: application/pdf
846578962ergfjksdghfv346bv
----part1--
Printing those extra headers shouldn't be too diffuclt, but I would have to
make sure that the attachments are in the right order. In particular, all
attachments that have a Content-ID that appears in the body should come before
all the others that don't. Do we know how Exchange sorts the attachments or is
there a way to control it? I think I've read somewhere on MSDN that attachments
should be sorted in the way they should be rendered. I would assume that this
means all the inline stuff comes before the real attachments, but I am not sure.
Is anyone familiar with this issue? I'd appreciate it if you could share some
thought and ideas.
thanks
dirk
--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
