Restricting End-User Message Release from Quarantine

Products

• Messaging Gateway

Issue/Introduction

In certain security configurations, administrators may wish to prevent end-users from independently releasing emails from the quarantine. Currently, the system does not support a direct "toggle" or setting to disable the Release button within the End-User Quarantine interface. This article outlines the current system behavior and provides a workaround to manage user expectations via custom notifications.

Cause

The End-User Quarantine is designed with a standard set of actions (Release, Delete, Whitelist) that are globally applied to the interface. Because these elements are part of the core UI framework, they cannot be selectively hidden or disabled through the standard policy configuration.

Resolution

Workaround: Custom Quarantine Notifications

Since the button cannot be removed, the recommended workaround is to use custom notifications that direct users to contact an administrator for message release, rather than relying on the automated interface.

Step 1: Create a Custom Notification Template

1. Navigate to Content > Resources > Notifications.

2. Click Add to create a new template.

3. Configure the notification to inform the recipient that their message has been held and provide specific instructions for release.

   • Example: Set the message body to: "A new message from $sender$ has been quarantined. If you would like to release this message, please contact [email protected]."

Step 2: Apply the Notification to Spam/Content Policies

1. Go to the specific policy (e.g., Email Spam Policy or Content Policy) where the quarantine action is defined.

2. In the Actions section, click Add.

3. Select the action to Send notification and choose the template created in Step 1.

4. Ensure the Hold message in Spam Quarantine action remains active.

5. Click Save.

Important Considerations

• Policy Precedence: If a user belongs to multiple policy groups, the system applies the policy from the group with the highest precedence (the group at the top of the list). Ensure your custom notification is applied to the highest-ranking group to ensure it triggers correctly.

• Feature Requests: If your organization requires a native functional change to disable the release button, a formal feature request must be submitted. Please provide a business justification and a detailed explanation of the requirement, which will be forwarded to our backend engineering team for review.