IBM AH0QXML User Guide - Page 37

Chapter 3. Domino 6 anti-spam architecture

25

this checking by specifying the hostname or IP address in an exclusion list. In

previous versions of Domino, when you implemented Relay controls your POP or

IMAP users were often prohibited from using Domino as a relay. Enhancements

made in this area now allow you to provide your authenticated users with the

ability to relay off the Domino server and not require relay control checking.

Although not documented to be a spam deterrent, a new notes.ini variable can

be used to disable routing internet mail to groups. By enabling

RouterDisableMailToGroups=1

, Internet messages sent to a group defined in

your Domino Directory will be failed.

Server Mail Rules

are new to Domino 6. Similar to mail file rules implemented

with the Notes client for a individual user in Release 5, server mail rules can be

configured to act on specific messages upon entry into your Domino

environment. You may choose to filter messages based on content, the number

of attachments, the type of attachments, the number of recipients, and many

other criteria. Messages containing questionable or offensive content can be

examined and moved to a quarantine database for further analysis.

3.3.2

User configuration features

Mail file rules allow the individual end-user to isolate messages by sender

address, domain, subject, or even by message body content. When creating

anti-spam mail file rules with the Notes client, end users can be specific and even

aggressive when defining the rules. End user can specify which actions are taken

on the identified spam messages, whether they want to file the messages for

further inspections and actions, or simple get rid of the unwanted messages.

Building anti-spam mail file rules should be seen as an additional measure in the

overall solution to the spam problem. Although configured by the end users with

their Notes client, mail file rules are enforced on the Domino server. Therefore,

they do use some server processing power, and having a large number of mail

file rules or several rules per user might have a performance impact on the

server. Because of this, your anti-spam campaign needs to be well planned, and

adequate direction on how to use mail file rules should be provided for the end

users.

3.4

Common problems and solutions

A numbers of features are available to help you manage common messaging and

e-mail problems. Each feature is particularly well suited to one or several specific

kinds of problems. The correspondence between some common problems and

the most appropriate features for solving them are shown in Table 3-1. Details for

the techniques identified are in the following text.

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 37

User configuration features, 3.4 Common problems and solutions

Page 37 highlights