IBM AH0QXML User Guide - Page 28

Summary, dealing with spam and how much of a priority it is for you. A solid spam

Page 28 highlights

More infrequently, it's a good idea to review your overall spam approach to see if it is still appropriate. You might want to re-survey your users periodically to see if the situation has improved from their perspective. It's also a good idea to occasionally appraise the technology landscape to see what the new approaches are to spam detection and prevention. There may be new Domino updates available or new techniques recommended to deter spam delivery. 2.2.6 Summary The old saying "An ounce of prevention is worth a pound of cure" is especially prescient when related to spam. Users that avoid providing their e-mail address to spammers receive less spam. Web sites that are careful to make themselves a difficult target for harvesters also result in less unsolicited mail. With enough prevention effort, spam should be a rare occurrence. If it does arrive, there are several methods of handling it: gateway-based, server-based, and user-based. The right approach depends on the stance that your organization takes when dealing with spam and how much of a priority it is for you. A solid spam prevention configuration needs to be monitored and adjusted over time. Reserve some time every week to analyze the effectiveness of your anti-spam configuration, and periodically revisit your approach to ensure that it is still consistent with what is required. Overall, much can be done to avoid and reduce spam delivery. 16 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

16
Lotus Domino 6 spam Survival Guide for IBM eServer
More infrequently, it's a good idea to review your overall spam approach to see if
it is still appropriate. You might want to re-survey your users periodically to see if
the situation has improved from their perspective.
It's also a good idea to occasionally appraise the technology landscape to see
what the new approaches are to spam detection and prevention. There may be
new Domino updates available or new techniques recommended to deter spam
delivery.
2.2.6
Summary
The old saying
An ounce of prevention is worth a pound of cure
is especially
prescient when related to spam. Users that avoid providing their e-mail address
to spammers receive less spam. Web sites that are careful to make themselves a
difficult target for harvesters also result in less unsolicited mail. With enough
prevention effort, spam should be a rare occurrence. If it does arrive, there are
several methods of handling it: gateway-based, server-based, and user-based.
The right approach depends on the stance that your organization takes when
dealing with spam and how much of a priority it is for you. A solid spam
prevention configuration needs to be monitored and adjusted over time. Reserve
some time every week to analyze the effectiveness of your anti-spam
configuration, and periodically revisit your approach to ensure that it is still
consistent with what is required. Overall, much can be done to avoid and reduce
spam delivery.