18.07.2013 Views

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring<br />

advanced antispam<br />

options<br />

Configuring advanced anti-spam options<br />

On the external side <strong>of</strong> the network, the mailertable should appear as:<br />

foo.comburbmailer-burb:localhost<br />

.foo.comburbmailer-burb:localhost<br />

where burb = the external burb number and Y = the internal (trusted)<br />

burb number.<br />

The entries that begin with a dot act as a wildcard, matching anything<br />

with that domain name. The entries that do not begin with a dot match<br />

the full domain name. See the /usr/share/sendmail/README file for more<br />

information on creating mailertables.<br />

7. Save the changes you made to file and then close the file.<br />

8. Click the Save icon to save the configuration changes and rebuild the<br />

configuration and database files. This will also automatically restart the<br />

sendmail servers.<br />

Using the Admin Console, you can configure the following advanced<br />

anti-spam areas:<br />

Configure the whitelist.cfg files to specify domains, IP addresses,<br />

and headers that will be allowed to pass through unmodified<br />

regardless <strong>of</strong> any rules that have been created. There is a separate<br />

whitelist.cfg file for the internal and external (Internet) burbs. For<br />

information on configuring a whitelist, see “Configuring the<br />

whitelist.cfg files” on page 11-13.<br />

Configure the policy.cfg file to determine the actions that will be<br />

taken by the spam filter on a per-burb basis when it encounters<br />

messages that are suspected to be spam. To configure the<br />

policy.cfg file, see “Configuring the policy.cfg file” on page 11-15.<br />

Caution: Modifying the authority.cfg files may prevent the spam filter from starting.<br />

Therefore, the authority.cfg file should not be modified.<br />

Configuring the whitelist.cfg files<br />

To configure a whitelist for the internal or external (Internet) burb, in<br />

the Admin Console select Services Configuration -> Servers and then<br />

select Spamfilter from the list <strong>of</strong> servers. Select the Advanced tab. The<br />

following window appears.<br />

Electronic Mail 11-13

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

Saved successfully!

Ooh no, something went wrong!