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.
I'm seeing exactly the same thing, jdroberson. It just started for me on Apr. 30. Only happens to replies or forwards done through OWA. I can confirm the differences in html you are seeing. Obviously the code that OWA creates is incorrect yet Entourage used to be able to render it anyway. I don't recall installing any Entourage updates recently but then I could have and don't remember it. Or could the MS patches you refer to mean Exchange patches? Just wondering where we could expect the fix to come from: Entourage or Exchange.
<jdrober...@stcloudstate.edu> wrote: > 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.
------------------------------------------------ Steve Hearn :: FileMaker 7 & 8 Certified Developer :: Manager, FileMaker Development CoreSolutions Development Inc. Web Site: http://www.coresolutions.ca London: (519) 641-7727 - Toronto: (416) 410-8649 ------------------------------------------------ software that works for you
I would have to think that the patch that caused the problem was on the Exchange side of things, as one of our Entourage clients was set to manual updates in Office 2004 and subsequently hasn't done any updates (ever. sigh.), and yet still has the problem. The April 30 time frame sounds about right, as we didn't have the problem before. I would expect the fix for this to come in the form of an Exchange patch.
"Steve Hearn" wrote: > I'm seeing exactly the same thing, jdroberson. It just started for me on > Apr. 30. Only happens to replies or forwards done through OWA. I can confirm > the differences in html you are seeing. Obviously the code that OWA creates > is incorrect yet Entourage used to be able to render it anyway. I don't > recall installing any Entourage updates recently but then I could have and > don't remember it. Or could the MS patches you refer to mean Exchange > patches? Just wondering where we could expect the fix to come from: > Entourage or Exchange.
> Steve
> On 5/2/06 4:20 PM, "jdrober...@stcloudstate.edu" > <jdrober...@stcloudstate.edu> wrote:
> > 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.
> ------------------------------------------------ > Steve Hearn > :: FileMaker 7 & 8 Certified Developer :: > Manager, FileMaker Development > CoreSolutions Development Inc. > Web Site: http://www.coresolutions.ca > London: (519) 641-7727 - Toronto: (416) 410-8649 > ------------------------------------------------ > software that works for you
I uninstalled MS KB911829 from the Exchange servers and this fixed the problem. Hopefully MS will release a patch to Entourage to handle malformed HTML better and a update the listed patch to Exchange so OWA doesn't create malformed HTML.
I apologize if this workaround has been noted but I am able to view the messages by opening them in a separate window (double click on the message). Then in the blank message body if you control click and then select "Auto Text Cleanup" from the pop up list and then select "Rewrap Paragraph" the text then shows up (you'll get some warning messages along the way).
On 5/9/06 8:18 AM, in article 1147187911.858627.39...@i39g2000cwa.googlegroups.com,
"mark.planocl...@doane.edu" <mark.planocl...@doane.edu> wrote: > I apologize if this workaround has been noted but I am able to view the > messages by opening them in a separate window (double click on the > message). Then in the blank message body if you control click and then > select "Auto Text Cleanup" from the pop up list and then select "Rewrap > Paragraph" the text then shows up (you'll get some warning messages > along the way).
Does that also change the HTML to plain text, or do you keep the HTML?
With some complex HTML messages, you'd first have to select Edit Message before Auto-Text Cleanup is available. As soon as you select Edit Message, it will convert to plain text. Still - you do get the text.
We applied the patch MS KB911829 May 10th and did not receive word that Entourage users had been affected until Monday, May 15th. We are running Exchange 2003 sp2 (patched OS and Exchange). The clients experiencing problems are Entourage 2004 sp2 and patched. Our configuration (exchange) is: 2 load balanced FE servers and two clusters (one active and one passive and the second cluster is 6 active and two passive, all servers are win2003sp1 and patched). All exchange servers are fully patched with MS KB911829. If we decide to uninstall this patch should it be uninstalled from all servers or only the FE servers. Any help or advice if other users are running a similar configuration would be appreciated.
We *always* keep front-end and backend server patchlevels in sync. Every time we've strayed from this we have had issues with frontend-backend connections. So i'd strongly suggest uninstalling everywhere :(
> We applied the patch MS KB911829 May 10th and did not receive word > that Entourage users had been affected until Monday, May 15th. We are > running Exchange 2003 sp2 (patched OS and Exchange). The clients > experiencing problems are Entourage 2004 sp2 and patched. Our > configuration (exchange) is: 2 load balanced FE servers and two > clusters (one active and one passive and the second cluster is 6 active > and two passive, all servers are win2003sp1 and patched). All exchange > servers are fully patched with MS KB911829. If we decide to uninstall > this patch should it be uninstalled from all servers or only the FE > servers. Any help or advice if other users are running a similar > configuration would be appreciated.
------------------------------------------------ Steve Hearn :: FileMaker 7 & 8 Certified Developer :: Manager, FileMaker Development CoreSolutions Development Inc. Web Site: http://www.coresolutions.ca London: (519) 641-7727 - Toronto: (416) 410-8649 ------------------------------------------------ software that works for you
