IBM AH0QXML User Guide - Page 107

Chapter 6. Third party anti-spam products

95

messages before they enter into your Domino system. Inbound message

attachments are first scanned for viruses, then they are processed by the

anti-spam filter module. If the message is determined to be spam, it is moved into

a separate junk mail folder. If not, the message is then passed on to the custom

message filter, and if not blocked during this process, it is delivered to the end

user as a valid e-mail message.

Administrators can create custom filters using a script language called

“

sieve.

”

Commands are available for complete control of inbound messages, including

generating replies, filing messages, redirection to a different e-mail address, and

acceptance or discarding of messages. Custom rules can be configured to

handle attachments and can act on attachments based on attachment type and

size. More information can be found on the BrightMail Web site at:

http://www.brightmail.com/enterprise-as.html

6.2.2

ActiveState PureMessage

PureMessage from ActiveState is a comprehensive e-mail filtering system for

spam protection, virus protection, and corporate policy enforcement.

Configurable filters provide full control over the security and usage of any

corporate e-mail system at the gateway level, protecting against productivity loss,

network downtime, and vulnerability of informational assets caused by

unsolicited or malicious e-mail.

PureMessage spam filter

The PureMessage spam filter safely identifies spam using a sophisticated suite

of heuristics, spam directories, and spam signatures. According to ActiveState,

customers experience over 80% spam filtering immediately upon installation,

increasing to accuracy levels in excess of 95% after basic filter tuning. To

maintain effectiveness against the evolving tactics of spammers, PureMessage

includes regular updates to the tests developed by the ActiveState anti-spam

response team. The result is an inbox clear of unsolicited e-mail.

The PureMessage system promotes end user productivity, protects against

liability caused by circulation of offensive materials, increases network efficiency,

and increases server security by protecting against denial of service and

directory harvest attacks. Flexible configuration options allow organizations to

uniquely define their spam identification and handling policies (for example

delete, quarantine, and archive).

How PureMessage spam filtering works

E-mail enters an organization via the Internet and is received by PureMessage

through its integrated mail transfer agent. E-mail is then filtered through a

comprehensive series of positive/negative tests to determine a spam probability

Section	Page
Front cover	1
Contents	5
Notices	7
Trademarks	8
Preface	9
The team that wrote this redbook	9
Become a published author	11
Comments welcome	12
Chapter 1. Introduction	13
1.1 Definition of spam	14
1.2 Categorizing spam	14
Chapter 2. Preventing unwanted e-mail and spam	19
2.1 Spam avoidance techniques	20
2.1.1 Passive harvesting attacks	20
2.1.2 Avoiding harvesting	21
2.1.3 Confusing the harvesters	22
2.1.4 Inform Users	22
2.2 How to block spam	24
2.2.1 At the gateway	25
2.2.2 At the server	25
2.2.3 By the end user	26
2.2.4 Selecting the best approach	26
2.2.5 Managing the ongoing anti-spam campaign	27
2.2.6 Summary	28
Chapter 3. Domino 6 anti-spam architecture	29
3.1 The Domino messaging environment	30
3.2 Domino 6 messaging components	32
3.2.1 SMTP Listener/Server	33
3.2.2 Router	35
3.3 Domino 6 anti-spam configuration	35
3.3.1 Server configuration features	36
3.3.2 User configuration features	37
3.4 Common problems and solutions	37
Chapter 4. Domino 6 Server anti-spam features	41
4.1 How to detect spam	42
4.1.1 Examining the message properties	42
4.1.2 Separating legitimate e-mail from spam based on content	43
4.2 Controlling connections from spammers	44
4.2.1 DNS Blacklist filters	44
4.2.2 Inbound Intended Recipients Controls	48
4.2.3 Disable routing mail to groups	51
4.2.4 Inbound connection controls	53
4.2.5 Inbound sender controls	54
4.3 Controlling delivery of spam	57
4.3.1 Server mail rules	57
4.4 Controlling use of your server as a relay	66
4.4.1 Inbound relay controls	66
4.4.2 Inbound relay enforcement	71
4.5 Protecting your Domino server from active address harvesting attacks	74
4.5.1 SMTP harvesting attacks	74
4.5.2 Spam mail bombing	74
4.5.3 Direct SMTP RCPT TO harvesting	74
4.5.4 Defending against active attacks	75
Chapter 5. Using mail file rules to prevent spam	77
5.1 Distinguishing between spam and legitimate e-mail	78
5.2 Mail file rules	80
5.2.1 Setting up mail file rules	80
5.2.2 Developing anti-spam mail file rules	83
5.2.3 Viewing mail rules and the evaluation sequence	89
5.2.4 Monitoring mail file rules	90
Chapter 6. Third party anti-spam products	93
6.1 Anti-spam products for Notes and Domino	94
6.1.1 spamJam for Lotus Notes and Domino	94
6.1.2 SpamEraser for Lotus Notes and Domino 6	97
6.1.3 iQ.Suite	100
6.1.4 ScanMail for Lotus Notes with eManager	101
6.1.5 XM SpamStop	104
6.1.6 Other anti-spam products for Notes and Domino	106
6.2 Anti-spam server and gateway products and services	106
6.2.1 BrightMail Anti-Spam 4.0 from BrightMail, Inc.	106
6.2.2 ActiveState PureMessage	107
6.2.3 Trend Micro Inc. products	109
6.2.4 Other anti-spam server or gateway products and services	110
Related publications	111
IBM Redbooks	111
Referenced Web sites	111
How to get IBM Redbooks	112
IBM Redbooks collections	112
Index	113

IBM AH0QXML User Guide - Page 107

ActiveState PureMessage, PureMessage spam filter

Page 107 highlights