IBM AH0QXML User Guide - Page 88

76

Lotus Domino 6 spam Survival Guide for IBM eServer

Filing mail with unacceptable body content

To scan the body of incoming e-mail, we choose the rule condition

When body

contains

. This type of rule uses up the most processing power on the server, and

should be created with that in mind. Having a lot of rules that scan the body of

e-mails can cause server performance problems. It is recommended that you

create only a few rules of this type for your mail, so you should be creative in

setting them up. By looking at the spam you have received in the past and

examining what the body of those e-mails contains, you can come up with some

very accurate rules that will catch most of the spam you receive. It is also

recommended that you file mail that matches on a scan of the body content

unless you are certain your rule is going to catch only spam.

Figure 5-7

Body scanning rule

In the example in Figure 5-7 we are scanning the body of incoming mail to see if

it contains the words

unsubscribe

and

offer

. If an e-mail contains both of these

words, the rule files it in our Incoming\Suspicious folder.

Filing e-mail from acceptable addresses and domains

As you develop your mail rules, keep in mind that acceptable addresses and

domains might be used by spammers to deceive you into thinking that their spam

e-mail is legitimate. You should consider your selection of acceptable addresses

and domains carefully. Remember also that public e-mail service domains seem

to be the preferred method of spoofing e-mail.

Figure 5-8 shows a rule to accept e-mail from specific addresses and domains.

Figure 5-8

Acceptable customers and vendors rule

In rules for filing e-mail, we recommend that you

do not

specifically file mail from

the domains of public e-mail services. Instead we recommend that you only file

e-mail from

full e-mail addresses

of legitimate senders within those e-mail

domains. Be aware that bulk emailers are seldom legitimate business concerns,

so they may create spoofed e-mail which appears to come from legitimate

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 88

Filing mail with unacceptable body content, Filing e-mail from acceptable addresses and domains

Page 88 highlights