|
The security updates added to SP3 are consistent with those in
Outlook 2003, with one exception: COM add-ins, VBA, and published
forms are not trusted as they are in 2003.
SP3 adds the Body, HTMLBody, WordEditor, and HTMLEditor properties to the list of properties
that trigger the security prompt. You'll need to update any software
which now triggers the security prompt. Since these properties
also trigger the prompt in Outlook 2003, most, if not all, add-ins should
have updated versions available now. Developers: see
OutlookCode.com for more information.
Programs known to be affected by the changes:
IHateSpam --
Update available
SpamNet --
Update available
Norton AntiSpam -- Run LiveUpdate.
HotBar, Smiley Central, and other ActiveX applications --
Uninstall or look for a newer version
Palm Pilot software -- remove
palmapp.dot from Word's startup folder
PocketMirror. Get the free
PocketMirror 3.1.6 update.
Palm's Hotsync v4.1.0
NewsGator --
More
information
Acrobat add-in for Word -- disable Word as the email editor
or disable the COM add-in in Outlook (instructions below)
**Note: If you previously edited the registry to fix this issue,
installing an update to Acrobat may reset the registry.
Other Word templates or add-ins may trigger the security
warning. Disable the add-in or Word as the editor or delete the
template from Word's startup folder.
Word Macros in normal.dot may cause the warning--rename
normal.dot and restart Word.
Incredimail for Outlook plugin -- update to
build 1431
NoHTML COM add-in. Disable this add-in and use the
readasplain registry key instead.
Classify for Outlook -- disable add-in until update is
available.
Scansoft PDF Converter Outlook Add-in -- disable or check
for an update from ScanSoft.
Spam Inspector (Giant Company)
Update to version 4.0.421
Ella for Spam
Control - disable or check for an update.
To disable add-ins, go to Tools, Options, Other, Advanced Options, COM Add-ins.
Remove the check from the add-in listing and close the dialogs.
For temporary workarounds, you can also use
ClickYes.
To prevent the Acrobat PDFMaker COM Addin from loading, go to
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Outlook\Addins\PDFMOutlook.PDFMOutlook
and change the LoadBehavior value from 3 to 2. Restart Outlook. The
PDF functions will still be available in Word and the other Office
programs. Note that installing Acrobat updates may reset the
registry key.
Additional file extensions are blocked by SP3:
asp
tmp
vsmacros
vss
vst
vsw
ws
Attachment Options was
updated to handle these types.
For a list of attachments blocked previously, see
Attachment Security.
You may receive a warning similar to:
Microsoft Word
c:\Program Files\Microsoft Office\Office 10\startup\palmapp.dot
contains macros. Macros may contain viruses.
If you don't use the template, remove it from the startup folder,
otherwise, disable Word as your email editor or use selfcert to sign
the macro, then trust all macros signed by selfcert. See
KB 217221 for more information on using selfcert.
If you are unable to access secure site (https) since installing
Service Pack 3, see
"The Page Cannot Be Displayed" Error Message When You Try to View Web Page on a Secure Web Site and use Method 2: Delete Your Existing
User Profile.
The preview pane displays the sender's name and address in
Display Name [email@address.com]
<email@address.com> format. This format is used on some, but
not all, opened messages.
The following issues are covered in more detail in Sue Mosher's
master article on the "object model guard" security
prompts and her accompanying article
for forms developers. Additional
information on the development issues is at
OutlookCode.com.
VBScript in forms won't run and folder home pages won't load in
folders in delegated/shared mailboxes. Use the SharedFolderScript
reg key to re-enable it on mailbox folder or PublicFolderScript reg
key to enable it on Public Folders.
HKCU\Software\Microsoft\Office\10.0\Outlook\Security
DWORD value = SharedFolderScript
DWORD value = PublicFolderScript
The forms cache is folder specific as it is in Outlook 2003..
ActiveX controls not marked safe for scripting won't load on
one-off forms. Note that this is different from the more restrictive
behavior in 2003 where all non-Outlook controls will not load on
one-off forms. The AllowActivexOneOffForms reg key doesn't apply to
Outlook 2002-SP3.
The <Filter> tag of the ViewXML property of the View Control
won't work unless it's on a folder home page (i.e. "trusted").
|