J
jdroberson
Since the latest round of MS patches (this week), some users have seen
messages come in with blank bodies in Entourage. They can see the body
of the message when reading it in OWA, or Outlook on a PC, etc. They
can also see the contents of the body if they view the source in
Entourage. After troubleshooting the issue for a little, I nailed the
problem down to happening under the following circumstances:
A rich client (IE on PC) user using OWA replies to, or forwards a
message to a recipient using Entourage. Things work fine if the OWA
user makes a New message, this only seems to be a problem when
forwarding or replying.
Looking at the differences between the source codes of the new message
that is visible in Entourage and a reply that is not visible in
Entourage shows some differences that would probably make more sense if
I knew my way around code but here goes my attempt to describe it:
In the messages that are visible in Entourage (New message from OWA)
the source code starts out with <html> then <head> followed by a bunch
of good stuff then a </head> to close that part out as would be
expected, followed by the body. In the messages that don't display
the body in Entourage, it starts with <HTML dri=ltr> then <HEAD>
followed by some other good stuff, but where I'd expect to see the
close head there's this instead <BASE href=HEAD>. There's no
</head> in the code at all. It just goes to the body after that line.
I might be missing something but this seems like a problem. Maybe most
browsers and email clients make the assumption that if they see the
body starting and don't see the head section closed, it's ok to
move onto the body, I'm not sure. I'd be interested to see if
anyone else out there can duplicate the problem.
I have Exchange 2003 servers patched to the current levels (OS and
Exchange). The OWA clients I've tested on are XP machines at various
patch levels and IE 6, and the Macs have current versions of Entourage.
messages come in with blank bodies in Entourage. They can see the body
of the message when reading it in OWA, or Outlook on a PC, etc. They
can also see the contents of the body if they view the source in
Entourage. After troubleshooting the issue for a little, I nailed the
problem down to happening under the following circumstances:
A rich client (IE on PC) user using OWA replies to, or forwards a
message to a recipient using Entourage. Things work fine if the OWA
user makes a New message, this only seems to be a problem when
forwarding or replying.
Looking at the differences between the source codes of the new message
that is visible in Entourage and a reply that is not visible in
Entourage shows some differences that would probably make more sense if
I knew my way around code but here goes my attempt to describe it:
In the messages that are visible in Entourage (New message from OWA)
the source code starts out with <html> then <head> followed by a bunch
of good stuff then a </head> to close that part out as would be
expected, followed by the body. In the messages that don't display
the body in Entourage, it starts with <HTML dri=ltr> then <HEAD>
followed by some other good stuff, but where I'd expect to see the
close head there's this instead <BASE href=HEAD>. There's no
</head> in the code at all. It just goes to the body after that line.
I might be missing something but this seems like a problem. Maybe most
browsers and email clients make the assumption that if they see the
body starting and don't see the head section closed, it's ok to
move onto the body, I'm not sure. I'd be interested to see if
anyone else out there can duplicate the problem.
I have Exchange 2003 servers patched to the current levels (OS and
Exchange). The OWA clients I've tested on are XP machines at various
patch levels and IE 6, and the Macs have current versions of Entourage.
