J
JBRC
Sorry this was a problem with my newsreader - I can now see the original posts.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
B
Brian Tillman
covaid hut said:any news?
Can you send me a sample as a .msg attachment? You might have to zip it up
first.
B
Brian Tillman
jbrc said:What was the original problem? I can't find any entry in the
newsgroup with this subject.
I have a problem with Outlook hanging under Vista so thought this may
be the same.
Not at all the same.
C
covaid hut
any news from microsoft???
my company is facing this problem coz users are switched to vista.....
my company is facing this problem coz users are switched to vista.....
B
Brian Tillman
covaid hut said: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.
C
covaid hut
what?
8o are they using vista plus outlook 2003 as a testing condition??
8o are they using vista plus outlook 2003 as a testing condition??
B
Brian Tillman
covaid hut said:what?
8o are they using vista plus outlook 2003 as a testing condition??
I imagine so. I have no knowledge of their testbed.
C
covaid hut
and the most important is, the problem happens when sending BCC mail(with attachments??)
feel very helpness, too bad
feel very helpness, too bad
B
Brian Tillman
covaid hut said:and the most important is, the problem happens when sending BCC
mail(with attachments??)
feel very helpness, too bad
I don't believe the presence of an attachment is germane.
C
covaid hut
Dear Brian ,
have u encountered this problem?
have u encountered this problem?
B
Brian Tillman
covaid hut said: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.
B
bardo
Have you solved?
Brian Tillman said: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.
B
Brian Tillman
bardo said:Have you solved?
Not yet.
L
Leighsa
Brian - do you have an update from your contact?
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
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
L
Leighsa
An exact replica of the error can be found here:
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
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
B
Brian Tillman
Leighsa said: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.
L
Leighsa
Thanks for your reply. I think I will initiate an SRX with
Microsoft.......and remind them that using Entourage or MacMail on both ends
will resolve the problem, as well.
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
Microsoft.......and remind them that using Entourage or MacMail on both ends
will resolve the problem, as well.
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
Q
QDC_Juha
Brian Tillman said: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.
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
B
Brian Tillman
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.
Q
QDC_Juha
Brian Tillman said: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!
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.