Sending HTML from Outlook to non-Outlook clients

From: Jim Walsh (DrJim_at_newsgroups.nospam)
Date: 12/08/04 

Date: Wed, 8 Dec 2004 11:02:18 -0500

This is a repost of this message. The first try got absolutely no responses.
Certainly, someone must know something about this.....

I have some correspondents that are using GroupWise as their e-mail client.

I have noted that they are usually unable to read e-mail that I send to them
that has been prepared and sent from Outlook using HTML format.

A search of this subject on the GroupWise support website turned up the
following information. I quote from their website:

<=============
The Novell GroupWise 6.5 Client and above determine that a document is to be
displayed in HTML by one of two methods.

1. The message has a first level attachment of Text.Html and the document
contains a tag like the following:

  <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">

  Note: The character set does not have to be "iso-8859-1" but it does have
to be a vaild character set. If text/html is specified without a character
set specification, the client will treat the document as plain text.

This tag tells the GroupWise client that the document is content Text/Html
and specifies a Character Set.

  2. The message has a Mime.822 atachment that specifices the following:
  Content-Type: text/html; charset=ISO-8859-1

  Note: Again, the Character Set does not have to be "iso-8859-1" but it
does have to be a vaild character set. If text/html is specified without a
character set specification, the client will treat the document as plain
text.

 The Novell GroupWise 6.5 and above client will only display a message in
HTML if both HTML and the Character Set are specified. HTML documents that
do not specify a character set could be a possible security violation. The
WC3 Standards Organization has some good information on the subject.

================>

When I look at the Internet header of HTML e-mail that I am sending from
Outlook, I observe the following:

Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_007C_01C4D7CC.91512150"

It appears to me that this is the cause of the problem. Does anyone know of
a way to have Outlook include an Internet header that would be compatible
with GroupWise, and, apparently the Internet standard?

Thanks for your help.

Jim

Relevant Pages

  • Sending Outlook HTML to GroupWise clients
    ... I have some correspondents that are using GroupWise as their e-mail client. ... that has been prepared and sent from Outlook using HTML format. ... and specifies a Character Set. ...
    (microsoft.public.outlook.general)
  • Re: Sending HTML from Outlook to non-Outlook clients
    ... can't tell you how to get the full source from GroupWise. ... Sue Mosher, Outlook MVP ... >> should be in an HTML message. ... >>> and specifies a Character Set. ...
    (microsoft.public.outlook.general)
  • Re: Sending HTML from Outlook to non-Outlook clients
    ... > that has been prepared and sent from Outlook using HTML format. ... > A search of this subject on the GroupWise support website turned up the ... > The Novell GroupWise 6.5 Client and above determine that a document is to ... > and specifies a Character Set. ...
    (microsoft.public.outlook.general)
  • Re: Sending HTML from Outlook to non-Outlook clients
    ... There is a configuration option in GroupWise to set the Compose ... > that has been prepared and sent from Outlook using HTML format. ... > The Novell GroupWise 6.5 Client and above determine that a document is to ... > and specifies a Character Set. ...
    (microsoft.public.outlook.general)
  • Re: Exporting as a web page
    ... Specify a different "Encoding" for the file when you save to HTML. ... regardless of whether you generate from a PC character set or a Mac ... If the Encoding is not specified in the file, the recipient browser will ... create a new message in Entourage with your document in the text body. ...
    (microsoft.public.mac.office.word)