Cisco Cisco Email Security Appliance C690 User Guide
Chapter 4 Quarantines
Configuring the IronPort Spam Quarantines Feature
4-48
Cisco IronPort AsyncOS 7.5 for Email Daily Management Guide
OL-25138-01
If, however, the user accesses the quarantine directly via a notification, or if the
authentication method is IMAP/POP, the quarantine will only display messages
for that user’s email address (or the address to which the notification was sent).
For more information about how end user authentication works, see
authentication method is IMAP/POP, the quarantine will only display messages
for that user’s email address (or the address to which the notification was sent).
For more information about how end user authentication works, see
Keep in mind that email addresses are case insensitive in the IronPort Spam
Quarantine, so for example, email for Admin@example.com and
admin@example.com will both be present in the quarantine for a user associated
with “admin@example.com.”
Quarantine, so for example, email for Admin@example.com and
admin@example.com will both be present in the quarantine for a user associated
with “admin@example.com.”
Limiting which Addresses have Mail Quarantined
You can use multiple mail policies (Mail Policies > Incoming Mail Policy) to
specify a list of recipient addresses for which mail will not be quarantined. Select
‘Deliver’ or ‘Drop’ instead of quarantine when configuring the anti-spam settings
for the mail policy.
specify a list of recipient addresses for which mail will not be quarantined. Select
‘Deliver’ or ‘Drop’ instead of quarantine when configuring the anti-spam settings
for the mail policy.
Default Encoding
AsyncOS attempts to determine the charset of a message based on the encoding
specified in the message headers. However, if the encoding specified in the
headers does not match that of the actual text, the message will not be displayed
properly when viewed in the IronPort Spam quarantine. This situation is more
likely to occur with spam messages.
specified in the message headers. However, if the encoding specified in the
headers does not match that of the actual text, the message will not be displayed
properly when viewed in the IronPort Spam quarantine. This situation is more
likely to occur with spam messages.
Specifying a Default Encoding
In the case where incoming email does not have a charset encoding specified in
the headers, you can configure your Cisco IronPort appliance to specify a default
encoding. Doing so will help ensure that these types of messages display properly
in the IronPort Spam quarantine.
the headers, you can configure your Cisco IronPort appliance to specify a default
encoding. Doing so will help ensure that these types of messages display properly
in the IronPort Spam quarantine.
However, specifying a default encoding can cause messages in other charsets to
display incorrectly. This applies only to messages that do not specify the encoding
in the message headers. Generally, you would only want to set a default encoding
if you expect the majority of your mail that falls into this category to be of one
specific encoding. For example, if the majority of your mail that gets quarantined
and that does not specify the charset encoding in the message headers is in
Japanese (ISO-2022-JP), you would select option 12 (in the
display incorrectly. This applies only to messages that do not specify the encoding
in the message headers. Generally, you would only want to set a default encoding
if you expect the majority of your mail that falls into this category to be of one
specific encoding. For example, if the majority of your mail that gets quarantined
and that does not specify the charset encoding in the message headers is in
Japanese (ISO-2022-JP), you would select option 12 (in the
scanconfig->setup