SpamLogic Settings

SpamLogic and related functionality does not work in the Exchange Gateway. If you are able to see it in the Gateway UI it is because it is peered with an Email Gateway.

SpamLogic settings define how the Gateway identifies spam, and the actions taken on messages identified as spam.

As an alternative or additional anti-spam defense, you can employ the Spam Detection clause in the What To Look For? section of content rules. Messages detected as spam by the Spam Detection clause can be copied to users' PMM areas and reviewed for false positives. The defined content rules can be applied to specific policy routes in order to provide further definition.

For a comprehensive spam policy, use the Spam Detection clause in your content rules in conjunction with the SpamLogic defenses defined on the SpamLogic Settings page.

If an upstream email relay exists between the Gateway and the originating SMTP host, certain spam defenses cannot be used. By specifying how the Gateway connects to the Internet using Connection Management, you determine the spam defenses that are available to use in your policy.

In addition to the above, you can use Address Validation to specify the addresses within your organization that can receive email through the Gateway. This is an effective way of stopping spam to invalid email addresses.

Allow List enables you to define a list of SMTP hosts from which the Gateway will accept email, regardless of the outcome of TRUSTmanager, RBL, SPFSender Policy Framework, or Greylisting checks.

You can also opt to block mail from specific countries or apply a weighting to suspicious countries if you suspect that spam messages are more likely to originate from them. Refer to Geoblocking for more information about configuring these settings.

See Configuring Spam Policy for information about configuring the SpamLogic settings.