ActiveX Error in Email Signature

[Will Niccolls]

Create a new email signature, now get ActiveX security error.

There is no picture in the signature, just an html link.

I can edit the signature htm file, but damn, its 140 lines!!! For a 10 line
signature!

I have passing familiarity with HTML but I have no idea which of those lines
invokes an activex object.

Can someone advise what to look for so I can delete it?

This is a simple siganature with some bold formatting and arial text.

There is no reason on earth it needs activex.

Thanks, Will

 

[Will Niccolls]

Does anyone understand why a simple signature would have an Active X object
in it? And how to delete the HTML code that creates it from the
signature.htm file?

Thanks!

 

[Guest]

I have same problem. The only way I can get round it is clicking on the use
Word 2003 as my editor option in Outlook. Did you manage to resolve problem?
Neil

 

[Guest]

I will give this one a bump as I am having the same error, started when I
switched from rtf to HTML to include an image
-michael

 

[Guest]

I found that the activex insertion is to enable address, email, etc tracking
hotlink click, to find address or whatever has the dotted underline showing
up, when using Word as your email editor.
You can deselect the "save smart tags ... so they can be used by the
recipient" in Word | Options | General | Email Options | General. This
doesn't always seem to work depending on how you edit your signature.
If you don't want the activex warning, or feature as some call it, make a
new signature or edit your signature with Word: Tools | Options | General |
Email Options. There you will find a basic text editor where you can select
font, color, etc. When you click OK to save the signature it saves it as a
word/html (also rtf & txt if you have options selected) and no activex
warnings.
This should not be confused with just using word to save as file type .html
as it will generate the required file types, but the html gives the activex
error.
This should also not be confused with using Outlook to edit the signature,
as instructed by all the how to's I could find, as the signatures edited with
Std editor will give colors in replys according to your Outlook reply color
option settings instead of the font colors used to make the file. Go Figure.
If you use the Outlook Advanced editor it's even more fun because you get a
true .html format which maintains font colors but it includes the activex.
As the saying goes, "works for me". Hope this helps someone.

Of course, the real question should be: why is a "sanctioned" activex
component causing the activex error?