> "Geir Magnusson Jr." wrote:
>
> My MSFT Outlook 2000 client tells me this is 'Plain Text', and because I am behind
>an 'Exchange Server', it's hard to tell what the real mail message was, so if this is
>still HTML, please let me know.
It's still HTML... because its multipart and the second part
is HTML. Netscape Communcator Mail then *allways* takes the
HTML version. Look at it yourself (sending emails to yourself)
and make sure you find a way to avoid multipart emails (if it
is not the server which is doing this crap).
I had similar discussions on TNEF attachments, which the senders
where claiming Outlook was doing it allright.
"Outlook and the Microsoft Exchange Client sometimes use a
proprietary method to package information for sending messages
across the Internet. This method is technically referred to as
Transport Neutral Encapsulation Format (TNEF).
A TNEF-encoded message contains a plain text version of the message,
and a binary attachment that "packages" various other parts of the
original message."
TNEF is far from being neutral, not even Outlook Express can read it
(now there exists a Perl module that extracts its contents), which
reminds one on the Halloween vs. Linux emails from M$.
The workaround for this is:
"Alternatively, for sending messages with regular file attachments,
TNEF is not needed. If you are sending e-mail with file attachments
to a recipient who does not use Outlook or the Exchange Client, you
should manually choose to use a mail format that does not require
TNEF (such as plain text). By not sending TNEF messages, the
recipient will be able to view and save the attachments as expected."
More to this can be found at:
http://support.microsoft.com/support/kb/articles/Q241/5/38.ASP
Maybe you can search the M$ site fore a solution to your/our (because
*we* get your HTML) problem.
:) Christoph
