Content filtering policies not triggering as expected on new Messaging Gateway scanners

Products

• Messaging Gateway

Issue/Introduction

Messages processed by a new scanner in a Messaging Gateway cluster are not triggering Content Filtering policies as expected, even when the message criteria clearly match an active policy.

Symptoms:

• Message Audit Logs (MAL) show the message passing through without the expected policy verdict.
• Message Audit Logs (MAL) show that the message has not been assigned to the expected policy group.
• The issue is isolated to one or more specific scanners, while other scanners in the same cluster process identical messages correctly.
• Outbound message filtering policies configured to resolve based on the recipient rather than sender are ignored by the affected scanner.

Environment

• Version: 10.9.2 and earlier

Cause

This issue occurs when a new scanner is added to an existing cluster and the "Resolve policies for outbound messages based on the recipient instead of the sender" global setting is enabled. The global setting is not added to the initial scanner configuration file resulting in the scanner assigning messages to unexpected policy groups.

Resolution

To resolve this issue, you must force the Control Center to rebuild and propagate the configuration files to all scanners in the cluster.

1. Log in to the Messaging Gateway Control Center.
2. Navigate to Protocols > Settings > Content Scanning.
3. Click the Save button without making any changes to the settings.

This will cause the configuration to be rebuilt and pushed to all scanners. This does not interrupt email flow or cause any service restarts and may be performed during normal operations.

This issue will be addressed in the 10.9.3 release.

Additional Information