Spam Policy

The Spam Policy tab on the SpamLogic Settings page enables you to configure how Secure Email Gateway handles spam at the perimeter before it needs to be processed by the Policy Engine.

Preparation

Before you start configuring the SpamLogic settings, ensure that your Gateway is set up properly to prevent future spam checks from failing. You must:

• Have a valid HTTP connection configured. Run the Connectivity Test to check this.

• Ensure that you have good, unrestricted DNS performance.

• Deal with any system alarms about reputation feeds and update services.

Configure Spam Policy

1. Navigate to Policy > Manage Policy Definition > SpamLogic Settings. The SpamLogic Settings page is displayed.

2. Select the Spam Policy tab.

Connection Management

• Specify how Secure Email Gateway is connected to the Internet. For further information, see Connection Management.

Spam Policy

• Specify the details of your spam policy.

  1. In the Spam Policy panel, click Click here to change these settings.

  2. Specify settings for each of the following:

     • If Reputation Good (see TRUSTmanager Reputation)
     • If Reputation Bad (see TRUSTmanager Reputation)
     • Real-time IP Blocklist
     • Spoof Detection
     • Validate Sender Domain
     • BATV Bounce Address Tag Validation Address Validation (see BATV)
     • DMARC Domain-based Message Authentication, Reporting & Conformance Reject (see DMARC)
     • DMARC Quarantine (see DMARC)
     • SPF Sender Policy Framework Hard Fail (see SPF)
     • SPF Soft Fail (see SPF)
     • DKIM DomainKeys Identified Mail Hard Fail (see DKIM)
     • DKIM Soft Fail (see DKIM)
     • Greylisting
     • Confirmed Junk Email (see Junk Email)
     • Suspected Junk Email (see Junk Email)

Suspected newsletter reclassification

• Specify if you wish suspected newsletters to be reclassified as spam.

  1. In the Suspected newsletter reclassification panel, click Click here to change these settings.
  2. Select the Reclassify suspected newsletters as spam check box to instruct the Gateway to regard suspected newsletters as spam. This enables organizations to customize their global response to incoming email newsletters.

Hold Junk Email in Message Area

• Specify the message area in which to hold phishing and other junk email messages.

  1. In the Hold Junk Email in Message Area panel, click Click here to change these settings.

  2. From the Select the message area to hold phishing messages in drop-down menu, select a message area.

     The default message area is Phishing. You can change this or create a new message area if required.

  3. From the Select the message area to hold all other Junk Email messages in drop-down menu, select a message area.

     The default message area is Spam. You can change this or create a new message area if required. For example, you might want to hold spam detected at the Gateway perimeter in one message area, and spam detected by your content rules in another.

  4. Click Save.

Perform spam checks on outbound messages

• Specify whether spam checks should be performed on outbound messages leaving your organization.

  1. In the Perform spam checks on outbound messages panel, click Click here to change these settings.
  2. Select the Enable spam checks on outbound messages check box to run the spam checks.
  3. Click Save.

Advanced Phishing Detection

• Specify whether advanced phishing detection using PhishTank is required. PhishTank is a collaborative clearing house for data and information about phishing on the Internet and provides links to known phishing sites so that any email arriving from these domains can be prevented from reaching your organization.

  1. In the Advanced Phishing Detection panel, click Click here to change these settings.
  2. Select the Enable PhishTank check box to enable the setting.
  3. Click Save.

  PhishTank is enabled by default on new installations of Secure Email Gateway, but is disabled upon upgrade from earlier versions to version 5.2.0. From version 5.2.0 onwards, any upgrade will preserve the setting in this section at the time the upgrade is initiated.

DKIM signing on outbound messages

• Specify if DKIM signing on outbound messages is required.

  1. In the DKIM signing on outbound messages panel, click Click here to change these settings.
  2. Select the Enable DKIM signing on outbound messages check box.
  3. If you have enabled DKIM signing on outbound messages, you can also select the If the message sender is empty, sign using the key for the domain of the From address check box optionally. This allows you to apply DKIM signing to messages such as out-of-office replies, which have empty message sender fields.
  4. Click Save.

  For more information on DKIM signing, see Spoof Detection.

Only accept messages for these addresses

• Specify the recipients who can receive email through the Gateway.

  1. In the Only accept messages for these addresses panel, click Click here to change these settings.
  2. Select the address list(s) that contain the users who will be allowed to receive email through the Gateway.
  3. Click Save.

Reject messages from the following

• Specify the senders who cannot send email through the Gateway.

  1. In the Reject messages from the following panel, click Click here to change these settings.
  2. Select the address list(s) that contain the users who will not be allowed to send email through the Gateway.
  3. Click Save.

3. Apply the configuration.

If you change any configuration or policy settings, you must Apply Configuration for the new settings to take effect. You can do this either from the Changes Made panel, or System > Configuration > Apply Configuration. See Apply new configuration for more information. If you use Peer Gateways (i.e. when multiple Gateways are peered), any configuration changes from a local Gateway can then be applied to all the peers at the same time. See Configure Peer Gateways for more information.

See also...

• Policy Routes
• What To Look For? clauses
• Accept or reject messages using Address Lists