IBM AH0QXML User Guide - Page 94

Anti-spam products for Notes and Domino, 6.1.1 spamJam for Lotus Notes and Domino

Page 94 highlights

6.1 Anti-spam products for Notes and Domino This section introduces some third party anti-spam products that operate in a Notes/Domino environment. These products add features to the anti-spam functionality provided by Notes/Domino. 6.1.1 spamJam for Lotus Notes and Domino spamJam for Lotus Notes and Domino is an adaptable filter designed to help administrators and end users detect and prevent spam. spamJam combines the best attributes of a centrally administered configuration with the flexibility of end user rule definition. End user message recovery is simple and immediately effective. This combined spamJam approach produces a system that administrators and users can trust to evaluate e-mail effectively, without the danger of losing or delaying important e-mail. Configuring spamJam spamJam allows mail administrators to define spam filters at the corporate level to prevent true spam, like pornography, while allowing individual users to define their own individual levels of spam control. For example, one user may want to see an unsolicited industry newsletter, while another may not. Administrators define the initial Master configuration and then the user takes over from there. The user can decide to leave their Master configuration as is, or define additional anti-spam criteria. Master configurations can be designated for "levels of aggressiveness," so administrators and users can apply spam controls that are more or less lenient, depending upon their specific spam problems. This also reduces the possibility of incorrectly categorizing desired e-mail as spam (false positives). In addition, once user configurations are defined, any changes to the corporate Master anti-spam configuration automatically update their corresponding user configurations. 82 Lotus Domino 6 spam Survival Guide for IBM eServer

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120

82
Lotus Domino 6 spam Survival Guide for IBM eServer
6.1
Anti-spam products for Notes and Domino
This section introduces some third party anti-spam products that operate in a
Notes/Domino environment. These products add features to the anti-spam
functionality provided by Notes/Domino.
6.1.1
spamJam for Lotus Notes and Domino
spamJam for Lotus Notes and Domino is an adaptable filter designed to help
administrators and end users detect and prevent spam. spamJam combines the
best attributes of a centrally administered configuration with the flexibility of end
user rule definition. End user message recovery is simple and immediately
effective. This combined spamJam approach produces a system that
administrators and users can trust to evaluate e-mail effectively, without the
danger of losing or delaying important e-mail.
Configuring spamJam
spamJam allows mail administrators to define spam filters at the corporate level
to prevent true spam, like pornography, while allowing individual users to define
their own individual levels of spam control. For example, one user may want to
see an unsolicited industry newsletter, while another may not.
Administrators define the initial Master configuration and then the user takes
over from there. The user can decide to leave their Master configuration as is, or
define additional anti-spam criteria. Master configurations can be designated for
levels of aggressiveness,
so administrators and users can apply spam controls
that are more or less lenient, depending upon their specific spam problems. This
also reduces the possibility of incorrectly categorizing desired e-mail as spam
(false positives). In addition, once user configurations are defined, any changes
to the corporate Master anti-spam configuration automatically update their
corresponding user configurations.