Re: Sending HTML from Outlook to non-Outlook clients
From: Jim Walsh (DrJim_at_newsgroups.nospam)
Date: 12/08/04
- Next message: Brian Tillman: "Re: emails showing in Inbox after running Rules"
- Previous message: Brian Tillman: "Re: body message html"
- In reply to: Sue Mosher [MVP-Outlook]: "Re: Sending HTML from Outlook to non-Outlook clients"
- Next in thread: Jim Walsh: "Re: Sending HTML from Outlook to non-Outlook clients"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 8 Dec 2004 15:18:00 -0500
Sue,
I don't understand what you are asking.
The problem that I am describing is the inability of GroupWise clients to
properly read e-mails using HTML format that I produce using Microsoft
Outlook. The knowledgebase article on the GroupWise website indicates what
the GroupWise client is looking for in order to properly recognize the
message as HTML.
So, I have the original messages that constitute the problem. I would be
happy to forward one to you for your examination to see where the problem
is.
Thanks again for your help.
Jim
"Sue Mosher [MVP-Outlook]" <suemvp@outlookcode.com> wrote in message
news:eWjr3TV3EHA.1188@tk2msftngp13.phx.gbl...
> That's not enough to tell us anything. Without the full message source
that
> shows the different message parts, we really can't tell what's being sent.
I
> can't tell you how to get the full source from GroupWise.
>
> --
> Sue Mosher, Outlook MVP
> Author of
> Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
>
> "Jim Walsh" <DrJim@newsgroups.nospam> wrote in message
> news:OXdfcUU3EHA.2016@TK2MSFTNGP15.phx.gbl...
> > Sue,
> >
> > Thanks for your quick reply to my posting. I was feeling kind of
abandoned
> > after no responses to my first try.
> >
> > Can you help with the basic problem, i.e. HTML messages prepared by
> > Outlook
> > are no readable by GroupWise, and the GroupWise knowledgebase article
> > seems
> > to imply that the problem is that Outlook is at fault.
> >
> > From a recent message I sent, here is the rest of the header (or at
least
> > as
> > much as I can find using View...Options):
> >
> > MIME-Version: 1.0
> > Content-Type: multipart/alternative;
> > boundary="----=_NextPart_000_002A_01C4D215.67BB2280"
> > X-Mailer: Microsoft Office Outlook, Build 11.0.6353
> > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> > Thread-Index: AcTSNC5KChgGowLjS8yJdhNJrf8+9wACvfEA
> >
> >
> > Jim
> >
> > "Sue Mosher [MVP-Outlook]" <suemvp@outlookcode.com> wrote in message
> > news:e9ZHsJU3EHA.2504@TK2MSFTNGP10.phx.gbl...
> >> multipart/alternative just tells you there are multiple parts, as there
> >> should be in an HTML message. The details about the individual parts
will
> > be
> >> farther down in the message source.
>
> >>
> >> "Jim Walsh" <DrJim@newsgroups.nospam> wrote in message
> >> news:eVUiw8T3EHA.3472@TK2MSFTNGP09.phx.gbl...
> >> >
> >> > 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
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>
- Next message: Brian Tillman: "Re: emails showing in Inbox after running Rules"
- Previous message: Brian Tillman: "Re: body message html"
- In reply to: Sue Mosher [MVP-Outlook]: "Re: Sending HTML from Outlook to non-Outlook clients"
- Next in thread: Jim Walsh: "Re: Sending HTML from Outlook to non-Outlook clients"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
