24.11.2012 Views

PureMessage for UNIX - Sophos

PureMessage for UNIX - Sophos

PureMessage for UNIX - Sophos

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.

sophos pureMessage <strong>for</strong> unix<br />

pureMessage architecture<br />

<strong>PureMessage</strong> is built around four major components (see Figure 1):<br />

6<br />

1.<br />

.<br />

.<br />

4.<br />

High-per<strong>for</strong>mance filtering engine<br />

Administrative interface<br />

Quarantine<br />

End user interfaces<br />

pureMessage engine<br />

<strong>PureMessage</strong>’s filtering engine serves two main purposes. Firstly, Sender<br />

Genotype connection-level control proactively protects against botnets, and<br />

per<strong>for</strong>ms reputation filtering, rejecting as many as 90% of connections and<br />

improving overall throughput and per<strong>for</strong>mance.<br />

Secondly, the <strong>PureMessage</strong> policy engine per<strong>for</strong>ms policy-level filtering on the<br />

message stream. The policy engine:<br />

•<br />

•<br />

•<br />

•<br />

Intercepts messages at the email gateway level (using built-in or external<br />

MTA).<br />

Scans the messages <strong>for</strong> spam, viruses and other conditions as defined by<br />

the message-filtering policy.<br />

Applies policy actions to the messages.<br />

Passes each message back to the MTA <strong>for</strong> delivery to the intended<br />

recipient, or quarantines the message <strong>for</strong> review in the <strong>PureMessage</strong><br />

quarantine.<br />

The order of the tests, test conditions, and actions applied to the message are<br />

all controlled by configuring the <strong>PureMessage</strong> inbound and outbound messagefiltering<br />

policy using the graphical <strong>PureMessage</strong> Manager interface.<br />

MTA<br />

<strong>PureMessage</strong> gateway<br />

MTA plug-in<br />

<strong>PureMessage</strong> engine<br />

Policy processor<br />

Email traffic<br />

<strong>PureMessage</strong> server<br />

Filtering<br />

<strong>PureMessage</strong> AV<br />

anti-virus filtering<br />

<strong>PureMessage</strong> AS<br />

anti-spam filtering<br />

<strong>PureMessage</strong><br />

policy filtering<br />

<strong>PureMessage</strong> quarantine<br />

Quarantine database<br />

Message store<br />

Figure 1: Main <strong>PureMessage</strong> components<br />

Administrator interface<br />

<strong>PureMessage</strong> Manager<br />

* Policy configuration<br />

* Quarantine management<br />

* Multi-server administration<br />

* Global allow list management<br />

* Reporting<br />

Delegated administrator interface<br />

* Policy opt-in/out<br />

* Quarantine management<br />

* List management<br />

* Reporting<br />

End-user interfaces (optional)<br />

Personal filter manager<br />

* End-user web interface<br />

* Personal allow and block lists<br />

* On-demand quarantine review<br />

* Personal preferences<br />

Personal quarantine digest<br />

* Email-based interface<br />

* Scheduled quarantine review

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

Saved successfully!

Ooh no, something went wrong!