That wasn’t' the content type I meant, but that does tell me something.
Content Type: multipart/mixed; indicates a plain text messages with
attachments.
multipart:/alternative indicates an HTML format message. And the
multipart/related indicates that the images were embedded in the message
body rather than simple attachments. For a sender using WLM that means
that the sender did an Insert, Image rather than Insert, File as
Attachment. If you are reading such a message in plain text (Tools,
Options, Read) then you should see the images listed as attachments with
the slide show option. If you are reading in HTML format, then the
images should be displayed in the message body.
The content type I was really interested in was the one with the encoded
images further down the message. Such a content type would be
Content-Type: image/jpeg;
I was wonder if the problem messages had a non-image type content type.
--
Mike -
http://TechHelp.Santovec.us
"CWLee" <> wrote in message
news:...
>
>
> "Michael Santovec" <> wrote:
>
>> Take a look at the message source (Ctrl-F3). Is the problem message
>> MIME encoded or Uuencoded?
>>
>> If MIME encoded, what is the Content Type for the images?
>
> OK, did that. Here are my findings:
>
> For an incoming email that works the way I like (i.e., the "View Image
> Slide Show" option is engaged): Mime encoded. Content Type:
> multipart/mixed; boundary="part1_d2e516da125.383dccda_boundry"
>
> For an incoming email that does NOT work the way I like: Mime encoded.
> Content Type:
> multipart/related;type="multipart:/alternative";boundary="----_=_nextpart_001_01ca6e06.e1805aa8"
>
> (Note that I may have misread, miscopied, or otherwise incorrectly
> shown one or more of the digits/characters as I attempted to transfer
> them from the incoming email to this message.)
>
> Does this information support your idea that the problem is due to a
> difference in the incoming messages?
>
> Thanks.
>
>