Symantec 10490452 Administration Guide - Page 87

subject contains inkjet, then inkjet, Inkjet, and INKJET in

Page 87 highlights

Configuring email filtering 87 Creating virus, spam, and compliance filter policies instead of deleted. When you are sure the compliance policies are working correctly, you can adjust the action. ■ Sieve scripts cannot be imported, including those created in previous versions of Symantec or Brightmail software. ■ There is no limit to the number of conditions per compliance policy. ■ Conditions can't be nested. ■ You can create compliance policies that block or allow email based upon the sender information, but usually it is best to use the Allowed Senders Lists and Blocked Senders Lists. However, it is appropriate to create compliance policies if you need to block or keep email based on a combination of the sender and other criteria, such as the subject or recipient. ■ The order of conditions in a filter does not matter as far as whether a filter matches a message. However, if a filter has Body tests, you can optimize the filter by positioning them as the final conditions in a filter. ■ Spammers usually "spoof" or forge some of the visible headers and the usually invisible envelope information. Sometimes they forge header information using actual email addresses or domains of innocent people or companies. Use care when creating filters against spam you've received. ■ The following considerations apply to keyword text string searches. For details on regular expression searches, see "Using Perl-compatible regular expressions in conditions" on page 91. ■ All tests for words and phrases are case-insensitive, meaning that lowercase letters in your conditions match lower- and uppercase letters in messages, and uppercase letters in your conditions match lower- and uppercase letters in messages. For example, if you tested that the subject contains "inkjet", then "inkjet", "Inkjet", and "INKJET" in a message subject would match. If you instead tested for "INKJET" in the subject, then "inkjet", "Inkjet", and "INKJET" would still match. This applies to all test types and all filter components. ■ Multiple white spaces in an email header or body are treated as a single space character. For example, if you tested that the subject contains "inkjet cartridge", then "inkjet cartridge" and "inkjet cartridge" in a message subject would match. If you instead tested for "inkjet cartridge" in the subject, then "inkjet cartridge" and "inkjet cartridge" would still match. This applies to all test types and all filter components. A message subject containing "i n k j e t c a r t r i d g e" would not match a test for "inkjet cartridge" or "inkjet cartridge".

  • 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
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258

87
Configuring email filtering
Creating virus, spam, and compliance filter policies
instead of deleted. When you are sure the compliance policies are working
correctly, you can adjust the action.
Sieve scripts cannot be imported, including those created in previous
versions of Symantec or Brightmail software.
There is no limit to the number of conditions per compliance policy.
Conditions can’t be nested.
You can create compliance policies that block or allow email based upon the
sender information, but usually it is best to use the Allowed Senders Lists
and Blocked Senders Lists. However, it is appropriate to create compliance
policies if you need to block or keep email based on a combination of the
sender and other criteria, such as the subject or recipient.
The order of conditions in a filter does not matter as far as whether a filter
matches a message. However, if a filter has Body tests, you can optimize the
filter by positioning them as the final conditions in a filter.
Spammers usually “spoof” or forge some of the visible headers and the
usually invisible envelope information. Sometimes they forge header
information using actual email addresses or domains of innocent people or
companies. Use care when creating filters against spam you’ve received.
The following considerations apply to keyword text string searches. For
details on regular expression searches, see
“Using Perl-compatible regular
expressions in conditions”
on page 91.
All tests for words and phrases are case-insensitive, meaning that
lowercase letters in your conditions match lower- and uppercase letters
in messages, and uppercase letters in your conditions match lower- and
uppercase letters in messages. For example, if you tested that the
subject contains “inkjet”, then “inkjet”, “Inkjet”, and “INKJET” in a
message subject would match. If you instead tested for “INKJET” in the
subject, then “inkjet”, “Inkjet”, and “INKJET” would still match. This
applies to all test types and all filter components.
Multiple white spaces in an email header or body are treated as a single
space character. For example, if you tested that the subject contains
“inkjet cartridge”, then “inkjet cartridge” and “inkjet
cartridge” in a
message subject would match. If you instead tested for
“inkjet
cartridge” in the subject, then “inkjet cartridge” and
“inkjet
cartridge” would still match. This applies to all test types and
all filter components. A message subject containing
“i n k j e t c a r t r i d g e” would not match a test for “inkjet cartridge” or
“inkjet
cartridge”.