G
Guest
I have figured out what is causing this and a way to fix it. I have read the
previous posts and a co-worker told me about changing the settings in the
restricted sites to allow these activex in unsecurely, but I did not want to
compromise the security settings.
Previously we had used Microsoft Word as the editor and html as the format
for emails. The signature file is the problem here, it has been changed and
when sending an email it will work fine with the MS editor checked and puts
in the correct signature. But when we try to send a reply the old signature
file comes into play and it changes it to html and throws this error message.
It also has the smart tags in it which might be part of the problem, I am
not sure.
I was able to fix it by checking the box to use MS Word as the editor and
this would allow the email to open with the HTML page and not throw that
exception error.
But still not good enough since this was supposed to be unchecked for our
company security policy.
But after trying several things like the repair etc I found that if I
deleted the signature file (copying it first) and then set it back up again
with a new one and pasting the signature back in and NOT using the advanced
(MS word as the advanced editor), and then selecting the new signature to be
on new emails and replies as well this fixed the problem. And any emails that
came in after that from other users that had the same signature problem I
would tell them how to correct this as well.
Actually I was going to write in and ask for help, but by testing out other
options I was able to fix it myself so I felt obliged to share it with all of
you. Hope this helps!
previous posts and a co-worker told me about changing the settings in the
restricted sites to allow these activex in unsecurely, but I did not want to
compromise the security settings.
Previously we had used Microsoft Word as the editor and html as the format
for emails. The signature file is the problem here, it has been changed and
when sending an email it will work fine with the MS editor checked and puts
in the correct signature. But when we try to send a reply the old signature
file comes into play and it changes it to html and throws this error message.
It also has the smart tags in it which might be part of the problem, I am
not sure.
I was able to fix it by checking the box to use MS Word as the editor and
this would allow the email to open with the HTML page and not throw that
exception error.
But still not good enough since this was supposed to be unchecked for our
company security policy.
But after trying several things like the repair etc I found that if I
deleted the signature file (copying it first) and then set it back up again
with a new one and pasting the signature back in and NOT using the advanced
(MS word as the advanced editor), and then selecting the new signature to be
on new emails and replies as well this fixed the problem. And any emails that
came in after that from other users that had the same signature problem I
would tell them how to correct this as well.
Actually I was going to write in and ask for help, but by testing out other
options I was able to fix it myself so I felt obliged to share it with all of
you. Hope this helps!