Tim:
The sample you provided, on a later email, has some JPEGs encoded into the message (as per the second description, above). But you didn't say if you were supplying a working or non-working sample.
Ed Greshko:
It wouldn't make much sense for him to have supplied a working example, would it? :-) :-)
Well, he did say some worked and some didn't. I'd be inclined to provide samples of both, for analysis.
Anyway, if you were to try view the mail in T-Bird you'd find it to be as originally described.
Don't have it installed, don't really like putting it on systems, either. I just had a quick scroll through the raw message (kind of hard, considering the rather huge content).
I had a bit more time to look at this in the evening and I can see what is being "expected" of T-Bird. If you look at the MIME headers for the images you'd these headers as an example....
Content-Type: image/jpeg Content-Transfer-Encoding: base64 Content-Disposition: inline Content-ID: <tAhk9iyMmm1CIfpU4g9p>
The "key" being the Content-ID.
Then, in the text/html section of the message you'd find this sort of html snippet....
<div class=3D"yiv3030508851ecxyiv7863957078MsoNormal" style=3D"=BACKGROUND:white;"><span style=3D"FONT-SIZE:16pt;FONT-FAMILY:Arial, sans-se= rif;COLOR:black;"><img id=3D"yiv3030508851ecxyiv7863957078_x0000_i1044" alt= =3D"[]" src=3D"cid:tAhk9iyMmm1CIfpU4g9p" width=3D"561" height=3D"405" data-= id=3D"17bfaf0f-58fa-c795-9880-bde833a43cb7"></span>
Notice the cid:tAhk9iyMmm1CIfpU4g9p? Which is referring to image via the "Content-ID"? I don't know what standard defines this, but it seems clear that the HTML engine of T-Bird can't handle this.
Yes, I remember that kind of thing, of old. I remember that it would flumux various emailers, back in my early days of using the internet. Though I can't recall which specific mail clients.