>How did I know the body is not encoded?
>
>For scores of over 20 the system forwards the email to an account that
>we check using Outlook Express. OE is better and easier to use for
>looking at the header since you can easily get the properties and then
>see the entire body and the header, whereas in Outlook you can't see an
>encoded body.
OE lets you see the raw E-mail, including the encoding? I didn't realize that.
> >From what I have seen so far, when a message is encoded the body is
>really unreadable. So in OE when you look at the message detail in the
>message property window it is all encoded.
>
>In the case of this eMail I saw the HTML body just like other emails but
>it had two attachments. So without the two attachments the body looked
>OK.
>
>Now I am probably not looking at the right thing.
It sounds like you are looking at the right thing -- with base64 encoding,
the MIME segment will display in a human-readable format, but when looking
at the raw E-mail, it won't be human-readable.
But, if one of the attachments was HTML (and had a "Content-type:
text/HTML" MIME header), and was base64 encoded, then it would still
trigger the test.
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
