IBM AH0QXML User Guide - Page 73

Chapter 4. Domino 6 Server anti-spam features

61

By default the inbound relay controls are enabled for external hosts. If the

connecting host

’

s IP address resolves to a name in one of the local Internet

domains, the host is considered internal. IP addresses that resolve to host

names outside the local Internet domains or that do not have DNS entries are

considered external. You can change this so that all or no hosts are subject to

the inbound relay controls.

±

“

Exceptions for authenticated users:

”

Specifies whether users who supply login credentials when connecting to the

server are exempt from enforcement of the inbound relay controls. Choose

one:

–

Perform anti-relay checks for authenticated users -

The server does not

allow exceptions for authenticated users. Authenticated users are subject

to the same enforcement as non-authenticated users.

–

Allow all authenticated users to relay -

Users who log in with a valid name

and password are exempt from the applicable inbound relay controls. Use

this to enable relaying by POP3 or IMAP users who connect to the network

from ISP accounts outside the local Internet domain.

This field provides an exception mechanism so that POP3 and IMAP users

will be able to send internet e-mail through this server.

±

“

Exclude these connecting hosts from anti-relay checks:

”

You create an exceptions list containing the IP addresses or host names of

hosts that relay to any permitted domain. For each specified exception, the

inbound relay controls will not be enforced. Enter the IP addresses or host

names of hosts to be exempted from the restrictions specified in the Inbound

relay controls section.

–

Enter IP addresses or host names of specific servers that should be able

to relay messages through this server.

–

IP addresses are entered in brackets. Wildcards can be used to indicate

all addresses in one subnet. Also ranges of addresses can be specified.

[156.16.25.1]

[156.16.25.*]

[156.16.25.128-255]

apps1.lotus.com

Note: You can use wildcards to represent an entire subnet address, but not

to represent values in a range. For example, [127.*.0.1] is valid;

[123.123.12-*.123] is not. If you want to specify a range, you can do it by

entering, for example [127.0.0.128-255].

–

Set the previous field to

“

All connecting hosts

”

and enter IP addresses or

host names of internal servers that are allowed to relay in order to prevent

unauthorized use of your SMTP servers by internal departments.

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 73

Perform anti-relay checks for authenticated users, Allow all authenticated users to relay

Page 73 highlights