Symantec 10744983 Administration Guide - Page 20

Where to get more information, Symantec Mail Security Planning Guide

Page 20 highlights

20 About Symantec Mail Security Where to get more information ■ The inbound MTA accepts the connection and moves the message to its inbound queue. ■ The Filtering Hub accepts a copy of the message for filtering. ■ The Filtering Hub consults the LDAP SyncService directory to expand the message's distribution list. ■ The Filtering Engine determines each recipient's filtering policies. ■ The message is checked against Blocked/Allowed Senders Lists defined by administrators. ■ Virus and configurable heuristic filters determine whether the message is infected. ■ Content Compliance filters scan the message for restricted attachment types, regular exessions, or keywords as defined in configurable dictionaries. ■ Spam filters compare message elements with current filters published by Symantec Security Response to determine whether the message is spam. At this point, the message may also be checked against end-user defined Language settings. ■ The Transformation Engine performs actions per recipient based on filtering results and configurable Group Policies. Where to get more information The Symantec Mail Security documentation set consists of the following manuals: ■ Symantec Mail Security Administration Guide ■ Symantec Mail Security Planning Guide ■ Symantec Mail Security Installation Guide ■ Symantec Mail Security Getting Started Symantec Mail Security also includes a comprehensive help system that contains conceptual and procedural information. You can visit the Symantec Web site for more information about your product. The following online resources are available: Provides access to the technical support Knowledge www.symantec.com/enterprise/support Base, newsgroups, contact information, downloads, and mailing list subscriptions

  • 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

The inbound MTA accepts the connection and moves the message to its inbound
queue.
The Filtering Hub accepts a copy of the message for filtering.
The Filtering Hub consults the LDAP SyncService directory to expand the
message's distribution list.
The Filtering Engine determines each recipient's filtering policies.
The message is checked against Blocked/Allowed Senders Lists defined by
administrators.
Virus and configurable heuristic filters determine whether the message is
infected.
Content Compliance filters scan the message for restricted attachment types,
regular exessions, or keywords as defined in configurable dictionaries.
Spam filters compare message elements with current filters published by
Symantec Security Response to determine whether the message is spam. At
this point, the message may also be checked against end-user defined Language
settings.
The Transformation Engine performs actions per recipient based on filtering
results and configurable Group Policies.
Where to get more information
The Symantec Mail Security documentation set consists of the following manuals:
Symantec Mail Security Administration Guide
Symantec Mail Security Planning Guide
Symantec Mail Security Installation Guide
Symantec Mail Security Getting Started
Symantec Mail Security also includes a comprehensive help system that contains
conceptual and procedural information.
You can visit the Symantec Web site for more information about your product.
The following online resources are available:
www.symantec.com/enterprise/support
Provides access to the technical support Knowledge
Base, newsgroups, contact information, downloads,
and mailing list subscriptions
About Symantec Mail Security
Where to get more information
20