12.07.2015 Views

WSM User Guide - WatchGuard Technologies

WSM User Guide - WatchGuard Technologies

WSM User Guide - WatchGuard Technologies

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Activating spamBlocker3 From Policy Manager, select Tasks > spamBlocker > Activate.The Activate spamBlocker wizard starts.4 Click through the wizard and add the information it asks for. The wizard has these screens:Apply spamBlocker settings to your policiesThis screen appears if you already have one or more SMTP policies defined on your Firebox but donot have spamBlocker enabled. From the list, select the proxy policies for which you want to enablespamBlocker. Any policies that have spamBlocker already enabled are grayed out. If you do not haveany SMTP policies defined at this time, this screen does not appear.Create proxy policiesThis screen appears if your Firebox does not yet have a policy created for SMTP. The wizard willcreate an SMTP proxy policy for you. You must have at least one external interface with a static IPaddress.To create an SMTP policy, enter the e-mail server IP address. The policy created by this wizardcontains “Any-External” for the From field and a static NAT entry for the To field. The static NAT entryuses the first static external IP address configured on the Firebox. It enables static NAT for the e-mailserver IP address you enter in the wizard. If this default static NAT SMTP policy is not the best choicefor your organization, you can use Policy Manager to create an SMTP policy before you use thewizard.Select the spamBlocker actionsUse this screen to select the spamBlocker actions for e-mail in the Spam, Bulk, and Suspectcategories.If you want to record log messages for a spamBlocker response, select the Log check box. If you donot want to record log messages, clear the Log check box.302 <strong>WatchGuard</strong> System Manager

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!