So, I have rolled out a new signature block to the users in our company using
a VBscript. However, now that the signature has been rolled out, some users
are reporting that Outlook now spell checks their signature block. This is a
problem since they have their e-mail addresses in their signature block,
along with some uncapitalized proper nouns that are there for visual appeal.

In the script I specified objSelection.NoProofing = True for the signature
text. When I open a new message in Outlook with Word as the editor I can see
that the NoProofing is set on that text, and it spell checks the message
properly, but our HTML stationery doesn't show up properly. When I open the
message with the Outlook editor, the HTML shows up properly but it spell
checks the signature block. Not on every user, just on about 20% of them.

I know that we can just add the misspelled words in the signature block to
the dictionary, but that doesn't really solve the problem. Is there a
registry setting that I am missing? What is the root cause of this?

Thanks in advance,
Mark

RE: Outlook 2003 Signature Spell Check by MarkStLaurent

MarkStLaurent
Wed Apr 02 15:55:01 PDT 2008

So, does anyone have any input on this problem?

"Mark St. Laurent" wrote:

> So, I have rolled out a new signature block to the users in our company using
> a VBscript. However, now that the signature has been rolled out, some users
> are reporting that Outlook now spell checks their signature block. This is a
> problem since they have their e-mail addresses in their signature block,
> along with some uncapitalized proper nouns that are there for visual appeal.
>
> In the script I specified objSelection.NoProofing = True for the signature
> text. When I open a new message in Outlook with Word as the editor I can see
> that the NoProofing is set on that text, and it spell checks the message
> properly, but our HTML stationery doesn't show up properly. When I open the
> message with the Outlook editor, the HTML shows up properly but it spell
> checks the signature block. Not on every user, just on about 20% of them.
>
> I know that we can just add the misspelled words in the signature block to
> the dictionary, but that doesn't really solve the problem. Is there a
> registry setting that I am missing? What is the root cause of this?
>
> Thanks in advance,
> Mark