By default, earlier versions of Outlook ran VBScript code in custom forms and scripts in folder home pages that were in public folders. This can be disabled by a policy setting or through the Outlook user interface. For more information about these settings, click the following article number to view the article in the Microsoft Knowledge Base: 838871 Description of the developer-related security changes in Outlook 2002 Service Pack 3 (SP3) In Outlook 2010, the default behavior was changed to prevent scripts from running in public folders. To re-enable this behavior in Outlook, follow these steps:
- Click File, and then click Options. (The screen shot for this step is listed below).
- In the list of categories, click Trust Center, and then click Trust Center Settings. (The screen shot for this step is listed below).
- In the left pane of the Trust Center, click E-mail Security. (The screen shot for this step is listed below).
- Select the Allow script in Public Folders check box, and then click OK.
BUG #: 73322 (Office14)
In Outlook 2010, the top-level public folder name changed from Public Folders to Public Folders - firstname.lastname@example.org to support multiple public folder stores being available in a single MAPI profile. Custom form code that refers to the top-level folder as Public Folders has to be updated so that the correct folder name is used with Outlook 2010. The following VBScript code sample shows how to dynamically return the correct folder name based on which version of Outlook is being used:
Set oSession = Application.GetNameSpace("MAPI")
If Left(Application.Version,2) < 14 Then
' Set public folder for Outlook 2007 and lower
GetTopLevelPublicFolderName = oSession.Folders("Public Folders")
' Set public folder for Outlook 2010 and higher
strUserName = oSession.CurrentUser.AddressEntry.GetExchangeUser.PrimarySMTPAddress
strFolderName = "Public Folders - " & strUserName
GetTopLevelPublicFolderName = oSession.Folders(strFolderName)
Outlook custom forms let form developer create custom actions that work like Reply, Forward, and so on. With a custom action, a form can be sent immediately instead of opening a new form, or users can be prompted to confirm that they want to send a form. If all the following conditions are true, Outlook does not send the form immediately, and the user is prompted to send the form:
- The form is a custom email message form (message class of IPM.Note or a subclass of IPM.Note).
- The modified action is one of the built-in actions: Reply, Reply to All, Forward, or Reply to Folder.
- The user selects the action in the Outlook user interface (the Action.Execute method in the Outlook object model is not affected).
This was a design change in Outlook 2010.
BUG #: 143295 (Office14)
If you use a custom message form and the form's actions are set to open a custom form on reply, reply all, or forward, then the message body will be blank after the reply or forward is sent. This only happens if the form is published in Outlook online mode. As a workaround, publish the form while Outlook is in cached mode. Because online mode is de-emphasized, there are no plans to fix this problem.
BUG #: 2273286 (Office15)