Activate and Configure spamBlocker

You can enable spamBlocker in SMTP, IMAP, and POP3-proxy policies. Before you enable spamBlocker, make sure you have met all requirements, as described in spamBlocker Requirements.

Activate spamBlocker

You can use a wizard to enable spamBlocker in existing SMTP, IMAP, and POP3-proxies and to add a new SMTP, IMAP, or POP3 proxy to your Firebox configuration.

When you use the wizard to enable spamBlocker for an existing proxy policy that uses a predefined proxy action, the wizard automatically creates a user-defined proxy action, enables spamBlocker in the new proxy action, and assigns that proxy action to the policy.

If you use the wizard to create an SMTP policy, the wizard creates a default SMTP-proxy policy, which uses static NAT. To create this default SMTP-proxy policy, your Firebox must have at least one external interface with a static IP address or PPPoE. The wizard adds only one policy even if you have more than one external interface. The To list of the policy has a static NAT entry (the static IP address of the first external interface to the specified email service IP address). If this default policy does not meet your requirements, add the SMTP-proxy policy before you use this wizard to enable spamBlocker.

After you use enable spamBlocker for your POP3, IMAP, or SMTP-proxy policies, you can edit the spamBlocker settings used for each proxy action.

Configure spamBlocker Actions

In the spamBlocker settings, you can configure spamBlocker actions for each proxy policy, and you can enable and disable spamBlocker for each proxy policy.

In Fireware Web UI, before you can enable spamBlocker manually for an SMTP, IMAP, or POP3-proxy policy, you must configure the policy to use a user-defined proxy action. To create a user-defined proxy action, you can clone the default (predefined) proxy action, and specify that proxy action in the proxy policy. To do this automatically, use the spamBlocker Activation Wizard, described in the previous section.

WatchGuard has retired the old spamBlocker engine used by Fireware versions lower than v12.5.4. If your Firebox runs one of these versions, you might see configuration options that are no longer supported. For more information, go to this Knowledge Base article.