IBM AH0QXML User Guide - Page 84

Incoming\Suspicious, Incoming\My Customers, Type of rule, Overall Anti-Spam, Effectiveness

Page 84 highlights

Table 5-1 Types of mail file rules with effectiveness and performance cost Type of rule Overall Anti-Spam Effectiveness Performance Cost Very Medium Less High Medium Low Address Blocking X X Domain Blocking X X Self-mail X X Subject Content X X Body Content X X Filing Acceptable Mail X X Note: In our examples we have used several folders and we are using rules to direct e-mail and spam e-mail into them. You don't have to use this same method to handle your mail. For example, you could use just a single folder for all mail you suspect to be spam without filing anything else automatically. You could send suspicious e-mail to another mail-in database, set an expiry date on the messages, or delete all of the suspicious e-mail. Pick the style that suits you best. Be careful when setting up rules that delete any mail, as deleted e-mail messages cannot be recovered. The anti-spam rule building technique that we show in this section is oriented toward the isolation and reduction of spam. This technique requires some review of the contents of various folders in the user's mail file. The folders used in this example are: Incoming\Suspicious - This folder is used to hold e-mail that our rules have determined to be suspicious and likely to be spam. Incoming\My Customers - This folder is used to hold incoming mail messages that our rules have determined to be from known customers and vendors. As a normal consequence of receiving e-mail, all users make an initial assessment of their inbound e-mail. However, as users develop anti-spam rules, they must make a qualitative analysis of the e-mails as they relate to the established mail rules. A user employing the technique in our example on their own mail file would have to periodically review all of the Incoming folders. The user must review the content of the Suspicious folder for false positives, that is, desired e-mails that were initially determined to be spam. At other times, the user must assess whether more stringent criteria are required to filter out more spam. 72 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

72
Lotus Domino 6 spam Survival Guide for IBM eServer
Table 5-1
Types of mail file rules with effectiveness and performance cost
The anti-spam rule building technique that we show in this section is oriented
toward the isolation and reduction of spam. This technique requires some review
of the contents of various folders in the user
s mail file. The folders used in this
example are:
±
Incoming\Suspicious
- This folder is used to hold e-mail that our rules have
determined to be suspicious and likely to be spam.
±
Incoming\My Customers
- This folder is used to hold incoming mail
messages that our rules have determined to be from known customers and
vendors.
As a normal consequence of receiving e-mail, all users make an initial
assessment of their inbound e-mail. However, as users develop anti-spam rules,
they must make a qualitative analysis of the e-mails as they relate to the
established mail rules. A user employing the technique in our example on their
own mail file would have to periodically review all of the Incoming folders. The
user must review the content of the Suspicious folder for false positives, that is,
desired e-mails that were initially determined to be spam. At other times, the user
must assess whether more stringent criteria are required to filter out more spam.
Type of rule
Overall Anti-Spam
Effectiveness
Performance Cost
Very
Medium
Less
High
Medium
Low
Address Blocking
X
X
Domain Blocking
X
X
Self-mail
X
X
Subject Content
X
X
Body Content
X
X
Filing Acceptable Mail
X
X
Note:
In our examples we have used several folders and we are using rules to
direct e-mail and spam e-mail into them. You don
t have to use this same
method to handle your mail. For example, you could use just a single folder for
all mail you suspect to be spam without filing anything else automatically. You
could send suspicious e-mail to another mail-in database, set an expiry date
on the messages, or delete all of the suspicious e-mail. Pick the style that suits
you best. Be careful when setting up rules that delete any mail, as deleted
e-mail messages cannot be recovered.