Configuring Local List Antispam (NSM Procedure)

This section includes the following topics:

Configuring Whitelist and Blacklist Entries

To configure local whitelist and blacklist custom objects:

  1. In the NSM navigation tree, select Device Manager > Devices.
  2. Click the Device Tree tab, and then double-click the device for which you want to configure whitelist and blacklist custom objects.
  3. Click the Configuration tab. In the configuration tree, select Security > Utm > Custom Objects.
  4. Select Url Pattern and click New.
  5. Enter a unique name for the list.
  6. Select Value and add a new entry.
  7. Enter a value for the URL pattern for whitelist or blacklist antispam filtering.

    Note: For URL pattern wildcard support, the wildcard rule is as follows: \*\.[]\?* and you must precede all wildcard URLs with http://. You can only use an asterisk (*) if it is at the beginning of the URL and is followed by a dot (.). You can only use a question mark (?) at the end of the URL.

    The following wildcard syntax is supported: http://*.juniper.net, http://www.juniper.ne?, http://www.juniper.n??. The following wildcard syntax is not supported: *.juniper.net , www.juniper.ne?, http://*juniper.net, http://*.

  8. Click OK to save the changes.

Configuring a Custom URL Category List Custom Object

To configure a custom URL category list custom object:

  1. In the NSM navigation tree, select Device Manager > Devices.
  2. Click the Device Tree tab, and then double-click the device for which you want to configure URL category list custom objects.
  3. Click the Configuration tab. In the configuration tree, select Security > Utm > Custom Objects.
  4. Select Custom Url Category and click New.
  5. Enter a unique name for the list.
  6. Select Value and add a new entry.
  7. Enter the name of the URL pattern list you created for bypassing scanning.
  8. Click OK to save the changes.

Configuring Server-Based Antispam

Antispam filtering allows you to use both a third-party server-based spam block list (SBL) and to optionally create your own local whitelists (benign) and blacklists (malicious) for filtering against e-mail messages. The antispam feature is not meant to replace your antispam server, but to complement it.

To configure server-based antispam:

  1. In the NSM navigation tree, select Device Manager > Devices.
  2. Click the Device Tree tab, and then double-click the device for which you want to configure server-based antispam.
  3. Click the Configuration tab. In the configuration tree, select Security > Utm > Feature Profile > Anti Spam.
  4. Select Symantec Sbl and enable the feature.
  5. Expand Symantec Sbl and select Profile.
  6. Add or modify antispam profile settings as specified in Table 227.
  7. Click one:
    • New—Adds a new profile.
    • OK—Saves the changes.
    • Cancel—Cancels the modifications.

Table 227: Server-Based Antispam Profile Settings

Option

Function

Your Action

Name

Specifies a name for the antispam profile.

Enter a unique name for the antispam profile.

sbl-default-server

Specifies whether the Symantec SBL server is used.

Select sbl-default-server if you are using the default server. Otherwise, select None.

Spam Action

Specifies the action to be taken by the device when spam is detected.

Select one of the following: tag-subject (of e-mail), block (e-mail), tag-header (of e-mail).

Custom Tag String

Specifies the string used for identifying a message as spam.

Enter a custom string for identifying a message as spam. By default, the device uses ***SPAM***.

Configuring a UTM Policy for SNMP

To configure a UTM policy for SNMP:

  1. In the NSM navigation tree, select Device Manager > Devices.
  2. Click the Device Tree tab, and then double-click the device for which you want to a UTM policy for SNMP.
  3. Click the Configuration tab. In the configuration tree, select Security > Utm > Utm Policy.
  4. Click New to add a new UTM policy entry.
  5. Enter a unique name for the UTM policy.
  6. Select Antispam and enter the name of the antispam profile.
  7. Click OK to save the changes.

Once you have configured a UTM policy for SNMP, attach the UTM policy to a security policy that you create.

Related Documentation