> I've done a lot of testing and the client AV is NOT a factor. Which is
> a good thing since the AV email scanning isn't something we'd want to
> disable.
Why, when there is no technical reason in the world to have it enabled? It
does NOT add to your safety and DOES interfere with Outlook operation.
> Again, it's the "Reply to" message content which retains integrity.
> It's the "Forward to" messages that lose the quoted content when viewed
> via Outlook, since the earlier message content becomes an .eml
> attachment.
>
> In Thunderbird or the web client (iPlanet Messenger Express) both types
> of messages display all content. So it appears that Outlook is
> truncating the attachment.
No, it appears that whatever generates the EML attachment is doing so in
such a way that Outlook cannot decode it properly.
> For grins, I tried Outlook Express 6. I assume this would also be
> subject to the desktop AV scanning (which is enabled) but maybe not.
It's possible that since the AV plug-in for OE and for Outlook are
different, one might interfere while the other doesn't. It's also possible
OE isn't as sensitive to the interference. Keep the integration if you
wish, but when you have trouble, the first thing you should so is eliminate
variables and uninstalling the AV (temporarily) at least, is warranted.
> Again, the "Reply to" message content is all intact.
> The "Forward to" message has a similar attachment that looks like:
> Fwd_ Re_ class.newcampaigns GSIP Quick Summary.eml (10.4 KB)
>
> When I open ^this I get a blank email with yet another attachment:
> class.newcampaigns GSIP Quick Summary (9.62 KB)
>
> Then when I open ^this I get the full message contents with all the
> quoted content. Sure looks to me like I'm losing that 9.62 KB of text
> with Outlook 2007, but where??
Now you have confirmation that it is the message itself that is malformed,
despite being viewable with Thunderbird. Clearly if OE has trouble as well;
it's the message content that is in error. It would be interesting to see
the raw message content. I suspect header malformation that is ignored by
Thunderbird or the web browser.
--
Brian Tillman [MVP-Outlook]
