03.02.2014 Views

ePrism User Guide - EdgeWave

ePrism User Guide - EdgeWave

ePrism User Guide - EdgeWave

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Email Spam Processing<br />

Email Spam Processing<br />

<strong>ePrism</strong> applies a series of filters to messages beginning with the simplest and proceeding to the<br />

most complex. The sequence is as follows:<br />

1. Various SMTP connection checks are performed for items such as unauthorized pipelining<br />

commands, non-FQDN senders, unknown sender domains, and so on.<br />

2. The source of the message is compared against a locally specified Specific Access Pattern.<br />

If found, it may be "rejected" or "accepted" for immediate delivery or relay.<br />

3. <strong>ePrism</strong> will apply locally specified attachment, malformation, and virus checks on the contents<br />

of the message.<br />

4. The message is passed through the OCF (Objectionable Content Filter) which searches for<br />

objectionable text within a message.<br />

5. The message is passed through Pattern Based Message Filters that look for a text or pattern<br />

match against a specified part of the message. If a filter rule is triggered, an associated action is<br />

executed such as "reject" or "accept" for immediate delivery. Any defined Trusted Senders will<br />

allow mail to bypass the rest of the spam controls.<br />

6. Mail is processed for spam only if it arrives from an "untrusted" source. This is defined as any<br />

system not on the local network or not specifically "trusted" by the administrator.<br />

7. The source of the message is checked to see it is listed on an RBL (Real-time Blackhole List), if<br />

enabled. The message may be rejected, quarantined, or tagged and delivered as required.<br />

8. The message is checked by DCC, if enabled, which reports if the message is "bulk" or has been<br />

reported on the Internet a certain number of times to be classified as "bulk". If this value<br />

exceeds the local threshold, the message may be rejected, quarantined, or tagged and delivered<br />

as required.<br />

9. The message is checked by STA, if enabled, to see if its contents exceed a locally specified<br />

threshold for spam. If so, the message may be rejected, quarantined, or tagged and delivered as<br />

required.<br />

10. Prior to delivery, <strong>ePrism</strong> will check to see if this message was relayed.<br />

See “Message Processing Order” on page 271 for a summary of the message processing order.<br />

99

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

Saved successfully!

Ooh no, something went wrong!