When I receive the message on my Outlook 2003/XP machine, the TO field shows
"undisclosed recipients", and the message displays correctly. The same
message on the Outlook 2003/Vista HP machine has the TO field empty, and the
message is displayed uninterpreted (with HTML codes showing for HTML
messages, etc.), and with all of the headers displayed.
This is a MAJOR problem with attachments since they come thru inline with
the text, and in an uninterpreted maner that makes it impossible to
reconstruct.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
What account type are you using?
If you have a virus scanner that integrates with Outlook disable this
integration and redownload the message.
--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more
-----
"JSmith" <JSm...@discussions.microsoft.com> wrote in message
news:22E86244-1EA3-4C9A...@microsoft.com...
I am using Norton Internet Securiy 2007 (version 10.3.0.12). I didn't see
any settings that directly referred to email, but I turned off "auto protect"
and resent the message. It still appears with the visible headers.
FWIW, another standard account on the same machine also receives this type
of messages with the headers visible.
Outlook 2003 on Vista, when receiving emails which were sent using the BCC
field (so "undisclosed-recipients" displays in the To: field), the raw email
is displayed complete with headers and MIME encoded attachments.
This has nothing to do with email scanners, as the Vista machine
encountering this problem is running Sophos anti-virus only, and is not
performing and email scanning/filtering.
The exact same email that was sent BCC'd will display fine on Outlook 2003
running on Windows XP - so it's not an issue with the formatting of the email
from the sender, but rather something to do with Vista screwing up Outlook
2003.
I've found another thread with others encountering this exact same problem.
http://www.zimbra.com/forums/administrators/8407-vista-outlook-2003-showing-mail-source.html
Is there some way to report this to Microsoft and get a hotfix made ? It's
really becoming a pain.
Does Microsoft monitor this newsgroup or can we report this issue
somewhere else?
Jo.
On Sep 12, 5:22 pm, Mike2ff99 <Mike2f...@discussions.microsoft.com>
wrote:
> Same problem. I even removed my antivirus completely, turned off the firewall
> and plugged directly into my non-firewalled cable router to download the
> message on my vista laptop. My XP w/Office2003machine decodes them fine. I
> use comcast cable, but the issue seems to happen most often from AOL users
> who send aBCCwith an empty TO: field..
>
> "JSmith" wrote:
> > The problem occurs on messages that are sent to me with ONLY "BCC" addresses.
>
> > When I receive the message on myOutlook2003/XP machine, the TO field shows
> > "undisclosed recipients", and the message displays correctly. The same
> > message on theOutlook2003/Vista HP machine has the TO field empty, and the
> > message is displayed uninterpreted (withHTMLcodes showing forHTML
> > messages, etc.), and with all of the headers displayed.
>
> > This is a MAJOR problem with attachments since they come thru inline with
> > the text, and in an uninterpreted maner that makes it impossible to
> > reconstruct.
>
> > ----------------
> > This post is a suggestion for Microsoft, and Microsoft responds to the
> > suggestions with the most votes. To vote for this suggestion, click the "I
> > Agree" button in the message pane. If you do not see the button, follow this
> > link to open the suggestion in the Microsoft Web-based Newsreader and then
> > click "I Agree" in the message pane.
>
> >http://www.microsoft.com/office/community/en-us/default.mspx?mid=22e8...
Any solution or hotfix yet??
This is having a huge impact on my business!!!
So, Microsoft....WHEN ARE YOU GOING TO FIX THIS?????????
Julie
My setup is as follows:
Email is POPed from Gmail.com and Verizon.net.
The received emails are OK when residing and viewed from the Gmail and
Verizon webmail sites. When POPed by Outlook 2003 HTML is often stripped out
and most non-PDF attachments are merged into the body of the email in the
form of machine code.
I have uninstalled and reinstalled Outlook to no avail.
OS = Vista
Vista firewall and auto updating are ON
Vista spyware and virus protection are OFF
Internet Security settings are DEFAULT
User account control is ON
All MS products have latest updates.
Norton Internet Security 10.4.0.13 w/latest updates
Disabling NIS does not make a difference.
--
JP
Any solutions?
Thanks
> I am also having this problem of the HTML code and pictures being
> displayed as text. It seems to happen when the TO field is blank but
> may happen in other circumstance. I'm running Office 2003 Outlook on
> a new Vista machine that has been updated with the service pack.
>
> Any solutions?
Not yet, but Microsoft knows about it.
--
Brian Tillman [MVP-Outlook]
> The problem occurs on messages that are sent to me with ONLY "BCC"
> addresses.
>
> When I receive the message on my Outlook 2003/XP machine, the TO
> field shows "undisclosed recipients", and the message displays
> correctly. The same message on the Outlook 2003/Vista HP machine
> has the TO field empty, and the message is displayed uninterpreted
> (with HTML codes showing for HTML messages, etc.), and with all of
> the headers displayed.
Microsoft would like me to send them screen shots of the problem and whether
or not Word is designated as the mail editor. Forward those things to me
ate the address with which I'm posting and I'll pass them on.
--
Brian Tillman [MVP-Outlook]
OK, but where is your email?
> OK, but where is your email?
Look on the message header.
--
Brian Tillman [MVP-Outlook]
> any news?
Can you send me a sample as a .msg attachment? You might have to zip it up
first.
--
Brian Tillman [MVP-Outlook]
my company is facing this problem coz users are switched to vista.....
> any news from microsoft???
>
> my company is facing this problem coz users are switched to vista.....
The latest news from my contact at Microsoft said that because the Outlook
team can't reproduce the problem when using Outlook as both the sending
client and the receiving client, that it's not a problem and they closed the
bug report. My contact is upset by that stance and has reopened the issue.
--
Brian Tillman [MVP-Outlook]
> what?
> 8o are they using vista plus outlook 2003 as a testing condition??
I imagine so. I have no knowledge of their testbed.
--
Brian Tillman [MVP-Outlook]
feel very helpness, too bad
I don't believe the presence of an attachment is germane.
--
Brian Tillman [MVP-Outlook]
have u encountered this problem?
> have u encountered this problem?
I have not, personally (since I don't use OL 2003 on a Vista machine), but
I've no doubt it's a problem for many.
--
Brian Tillman [MVP-Outlook]
> Have you solved?
Not yet.
--
Brian Tillman [MVP-Outlook]
If the reason for the lack of attention on this issue truly is that
Microsoft cannot reproduce the error, I will be happy to send them a machine
that DOES produce the error.
And an additional note that I did not see documented to this point: if you
forward the misbehaving email to someone who uses XP instead of Vista and
they forward it back to the Vista user, the html is correctly presented.
Any assistance you can offer will be appreciated
Leighsa
http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=1&SiteID=1&PageID=1&PostID=849645
and the error is quite well documented all over the internet - google it.
Hopefully this will eliminate the need for screen shots.
Any assistance you can offer will be appreciated - especially by your
contact at Microsoft.
Leighsa
> Brian - do you have an update from your contact?
Nope, sorry.
> If the reason for the lack of attention on this issue truly is that
> Microsoft cannot reproduce the error, I will be happy to send them a
> machine that DOES produce the error.
The most recent update I have (several weeks ago) said that the since using
Outlook on BOTH ends (sending and receiving) prevents the problem, the
Outlook team considers the problem solved. Both I and my Microsoft contact
consider that bogus.
--
Brian Tillman [MVP-Outlook]
My venom is not directed at you - I (and my 300 clients) are tired of the
whole "Vista" debacle. It makes about as much sense for Microsoft to drop XP
as it would have for Ford to drop all models but the Pinto in the '80's.
Thanks, again.
Leighsa
"Brian Tillman" wrote:
> The latest news from my contact at Microsoft said that because the Outlook
> team can't reproduce the problem when using Outlook as both the sending
> client and the receiving client, that it's not a problem and they closed the
> bug report. My contact is upset by that stance and has reopened the issue.
> --
> Brian Tillman [MVP-Outlook]
>
I have been experiencing this same issue since upgrading to Vista in October
and have been waiting for it to be resolved. I find the attitude of
Microsoft incomprehensible. If it is a question of a faulty specification
document or implementation by Microsoft it's only logical that the problem
might not show up between two clients using the same wrong spec. As far as I
know, e-mail is meant to be a tool to use for communicating with anyone and
everyone and not just within a legacy environment.
I recently stumbled over the same attitude when I failed to copy a large
file (2 Gb) using Vista on our Samba network. The copy had worked for
smaller file sizes, but I apparently hit some sort of a limit and it ceased
to work. A support call to Microsoft ended in the support person stating
that they cannot do anything as it is not a Microsoft network.
It's like BMW saying that we are sorry your car went off the road, but we
can't do anything, because we didn't build the road.
(The copying now works without problems on Vista over the same network after
getting a third party application to do the job.)
-- Juha
> I have been experiencing this same issue since upgrading to Vista in
> October and have been waiting for it to be resolved. I find the
> attitude of Microsoft incomprehensible. If it is a question of a
> faulty specification document or implementation by Microsoft it's
> only logical that the problem might not show up between two clients
> using the same wrong spec. As far as I know, e-mail is meant to be a
> tool to use for communicating with anyone and everyone and not just
> within a legacy environment.
Apparently, one part of Microsoft didn't realize another part of Microsoft
found the source of the problem and created a hotfix. As far as I know, the
hotfix is not public yet, but a message describing it and how to obtain it
has been posted in one of these newsgroups, but I can't find it right now.
--
Brian Tillman [MVP-Outlook]
"Brian Tillman" wrote:
> Apparently, one part of Microsoft didn't realize another part of Microsoft
> found the source of the problem and created a hotfix. As far as I know, the
> hotfix is not public yet, but a message describing it and how to obtain it
> has been posted in one of these newsgroups, but I can't find it right now.
Please post information on the hotfix here when/if you find it. Thanks!
> Please post information on the hotfix here when/if you find it.
It's public now. See http://support.microsoft.com/kb/951982
--
Brian Tillman [MVP-Outlook]
I am most certainly having the same problem as everyone else running Vista
and Outlook 2003 when receiving blind copies.
Thanks.
> I appreciate all your efforts on this Brian. Unfortunately this
> patch does not seem to solve the problem...at least for me. I will
> be interested to learn if this works for anyone else.
>
> I am most certainly having the same problem as everyone else running
> Vista and Outlook 2003 when receiving blind copies.
Other people have reported that it does fix the issue.
--
Brian Tillman [MVP-Outlook]
> Brian, have you heard anything from microsoft about a possible fix
> for this issue? It's still being produced after installing the
> hotfix.
Other people who installed the hotfix reported that it solved the problem.
--
Brian Tillman [MVP-Outlook]
I tried the Hotfix 951982 and I get an error code 40 ( not all files successfully unzipped) when it unzips.
Just to add to the mix of frustrations over this ongoing issue. Interesting that some did find it solved the problem though. :?
any suggestion appreciated.
"JSmith" wrote:
> The problem occurs on messages that are sent to me with ONLY "BCC" addresses.
>
> When I receive the message on my Outlook 2003/XP machine, the TO field shows
> "undisclosed recipients", and the message displays correctly. The same
> message on the Outlook 2003/Vista HP machine has the TO field empty, and the
> message is displayed uninterpreted (with HTML codes showing for HTML
> messages, etc.), and with all of the headers displayed.
>
> This is a MAJOR problem with attachments since they come thru inline with
> the text, and in an uninterpreted maner that makes it impossible to
> reconstruct.
>
>
> ----------------
> This post is a suggestion for Microsoft, and Microsoft responds to the
> suggestions with the most votes. To vote for this suggestion, click the "I
> Agree" button in the message pane. If you do not see the button, follow this
> link to open the suggestion in the Microsoft Web-based Newsreader and then
> click "I Agree" in the message pane.
>
> http://www.microsoft.com/office/community/en-us/default.mspx?mid=22e86244-1ea3-4c9a-af2c-04740a123591&dg=microsoft.public.outlook.general
--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Outlook Tips by email:
mailto:dailytips-sub...@lists.outlooktips.net
EMO - a weekly newsletter about Outlook and Exchange:
mailto:EMO-NEWSLETTER-S...@PEACH.EASE.LSOFT.COM
You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.
"Ole Smith-Hansen" <Ole Smith-...@discussions.microsoft.com> wrote in
message news:120CD63A-BBE8-4FD6...@microsoft.com...
Office 2003 Service Pack 3
Update for Microsoft Windows KB957388
Update for Outlook 2003 KB953432
Outlook 2003 hotfix KB951982
You should laugh at them telling me they had never heard of this issue. I
proceeded to send them a link to their own message board documented the
problem back from the very beginning. I hope this helps everyone still
having issues.