Tom B" wrote in said:
And YI means what? We don't do texting here.
have a an user on outlook 2003 IE 7
So with which program do you want help? You named 2 programs.
that recently started getting thsi message when replying to HTML
emails.
We aren't there looking over your shoulder to see WHAT message you are
pointing at. So far, questions but no identification of the problem.
We did a reset on IE7 to defaults
And how would that help with some unidentified "message" or problem in Outlook?
but that didn't resolve the issue.
As expected. You're tweaking IE, not Outlook.
Is this possible a problem with the signature?
Don't know. You haven't yet mentioned what was the problem.
Or is there another cative x setting that could be changed in office?
Don't know. Still don't know what is the unidentified "message".
The error says: One or more cative x controls could not be displayed:
1. current security setting prohibit display
2. You have blocked a publisher.
Ah, so, you ask questions but where you only identify at the end on what
you based your questions. Please don't ask questions in the prose of a
mystery writer that leaves it until the end of the last chapter to
expose the culprit.
Outlook is, by default, configured to use the Restricted Sites security
zone. That means scripts are not allowed to run inside of HTML-
formatted e-mails. Don't expect web pages designed for rendering by
web browsers to behave the same inside of e-mail clients. HTML
formatting for e-mails is much more limited than for web sites. No
recipients (or a rare few) want scripts running on their host when they
are reading e-mails.
The vast majority of e-mail users will not allow scripts to execute on
their host when reading e-mails. Since you mention this user is
replying, I suspect they are using an HTML template that includes a
reference to a script (ActiveX) control (which they may have but cannot guarantee that
the recipient has, and which will be neutered in the recipient's e-mail
client, anyway). You'll have to see how they are composing their
reply.
Yes, they might be referencing a script control in their signature.
Easy way to check is to tell this user NOT to use signatures when they
compose e-mails and see if the warning goes away. The signature
becomes part of the e-mail message, so whether the ActiveX control is
referenced in the body or the signature (which becomes part of the
body) makes no difference. This user will have to get rid of the
scripting in their e-mail whether in the body or by a signature that
gets appended to the body upon sending the message.
