We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

How to Retrieve Stubbed Messages in Shared Mailboxes

  • Last updated on

This article refers to the Barracuda Message Archiver firmware version 5.2 or higher, and Barracuda Archive Search for Outlook version 5.2 or higher. Barracuda Archive Search for Outlook supports Outlook versions 2010, 2013, and 2016.

Verify Barracuda Archive Search for Outlook version (available for download on the USERS > Client Downloads page) is the same major revision as the Barracuda Message Archiver firmware.

Configuration Guidelines
This article is intended as a configuration guideline; your deployment will be specific to your environment. Any administrative changes should be reviewed with your IT team before proceeding.

 

Use the steps described in this article if Outlook users are able to forward stubbed attachments or emails from their own Outlook mailbox, but not from a shared Outlook mailbox. If this is the case, users will receive an error message from Outlook similar to: "Unable to open original message" when attempting to forward stubbed attachments from a shared Outlook mailbox.

By default, in Microsoft Outlook 2010 a security setting does not allow script execution or custom forms in shared mailboxes or public folders. For this reason, if the Microsoft Exchange Administrator performs message stubbing on shared mailboxes or public folders delegated to all users or specific user groups, these stubbed messages cannot be retrieved in Barracuda Archive Search for Outlook. To allow users to retrieve these stubbed messages in addition to their INBOX messages, each user can set Allow Script in shared folders, or the Microsoft Exchange Administrator can enable scripts in folders organization-wide using the Microsoft Office policy template (ADM) files. 

Microsoft Outlook 2013 / 2016
In Microsoft Outlook 2013 and 2016, script execution is allowed by default.

Enable Scripting Organization-Wide (Recommended)

To enable scripts across your entire organization,see the Microsoft article Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool download, verify your operating system in the section System requirements, and following the steps described in the section Instructions.

Once you download and set up the ADM template files, open the ADM file outlk14.adm.

In the ADM file, set VALUEON NUMERIC to '1' and VALUEOFF NUMERIC to '0' for the following values:

  • VALUENAME SharedFolderScript
  • VALUENAME PublicFolderScript

For example:

POLICY !L_DisableOutlookobjectmodelscripts

KEYNAME Software\Policies\Microsoft\Office\14.0\Outlook\Security

VALUENAME SharedFolderScript

VALUEON NUMERIC 1

VALUEOFF NUMERIC 0

EXPLAIN !L_DisableOutlookobjectmodelscriptsExplain

END POLICY

POLICY !L_DisableOutlookobjectmodelscriptsforpublicfolders

KEYNAME Software\Policies\Microsoft\Office\14.0\Outlook\Security

VALUENAME PublicFolderScript

VALUEON NUMERIC 1

VALUEOFF NUMERIC 0

EXPLAIN !L_DisableOutlookobjectmodelscriptsforpublicfoldersExplain

END POLICY

END CATEGORY

Enable Scripts on User Systems

If you do not wish to use ADM templates to allow scripting across the entire organization, you can direct each user to enable scripts for shared and public folders. Use the following steps to enable scripts in shared and public folders in Outlook 2010:

  1. Log in to Microsoft Outlook 2010.
  2. On the File menu, click Options.
  3. In the Navigation Pane, click Trust Center, and then click Trust Center Settings.
  4. In the Navigation Pane, click E-mail Security, and in the Script in Folders section, select Allow script in shared folders and Allow script in Public Folders:
    encrypt_email.png
  5.  Click OK to save your settings.
Last updated on