Symantec 10744983 Administration Guide - Page 66

Configuring scanning settings, Settings > Invalid Recipients, Dropmessagesforinvalidrecipients

Page 66 highlights

66 Configuring email settings Configuring scanning settings To configure invalid recipient handling 1 In the Control Center, click Settings > Invalid Recipients. 2 Do one of the following: ■ Uncheck Drop messages for invalid recipients to return bounce messages to the sender for invalid addresses. ■ Check Drop messages for invalid recipients to drop invalid messages from the mail stream and return no bounce messages to the sender. For this setting to take effect, a full synchronization and replication cycle must be completed. This setting is independent of the Directory Harvest Attack Email Firewall policy, and can be used in conjunction with it. 3 Click Save. Configuring scanning settings Use the Scanning Settings page to configure container settings and content filtering settings. Configuring container settings When Symantec Mail Security processes certain zip files and other types of compressed files, these files can expand to the point where they deplete system memory. Such container files are often referred to as "zip bombs." Symantec Mail Security can handle such situations by automatically sidelining large attachments and stripping the attachments. There is a presumption that such a file can be a zip bomb and should not be allowed to deplete system resources. The file is sidelined only because of its size, not because of any indication that it contains a virus. You can specify this size threshold and the maximum extraction level that Symantec Mail Security will process in memory, as well as a time limit for scanning containers. If the configured limits are reached, Symantec Mail Security will automatically perform the action designated for the "unscannable" category in the Group Policies settings.

  • 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

To configure invalid recipient handling
1
In the Control Center, click
Settings > Invalid Recipients
.
2
Do one of the following:
Uncheck
Dropmessagesforinvalidrecipients
to return bounce messages
to the sender for invalid addresses.
Check
Drop messages for invalid recipients
to drop invalid messages
from the mail stream and return no bounce messages to the sender. For
this setting to take effect, a full synchronization and replication cycle
must be completed.
This setting is independent of the Directory Harvest Attack Email Firewall
policy, and can be used in conjunction with it.
3
Click
Save
.
Configuring scanning settings
Use the Scanning Settings page to configure container settings and content
filtering settings.
Configuring container settings
When Symantec Mail Security processes certain zip files and other types of
compressed files, these files can expand to the point where they deplete system
memory. Such container files are often referred to as “zip bombs.” Symantec Mail
Security can handle such situations by automatically sidelining large attachments
and stripping the attachments. There is a presumption that such a file can be a
zip bomb and should not be allowed to deplete system resources. The file is
sidelined only because of its size, not because of any indication that it contains a
virus.
You can specify this size threshold and the maximum extraction level that
Symantec Mail Security will process in memory, as well as a time limit for scanning
containers. If the configured limits are reached, Symantec Mail Security will
automatically perform the action designated for the “unscannable” category in
the Group Policies settings.
Configuring email settings
Configuring scanning settings
66