27.11.2012 Views

IronPort - daily management guide - AsyncOS 7.6.1

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Working with Messages in System Quarantines<br />

4-16<br />

Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email Daily Management Guide<br />

Chapter 4 Quarantines<br />

The GUI only shows the scheduled exit time from the quarantines to which the user has access. (For<br />

a given message, there is a separate exit time for each quarantine.)<br />

The GUI will show whether the message is also stored in any other quarantines:<br />

Figure 4-11 Searching Quarantines<br />

The user will not be told the names of the other quarantine(s) holding the message.<br />

Releasing a message only affects the queues to which the user has access.<br />

If the message is also queued in other quarantines not accessible to the user, the message will remain<br />

in quarantine, unchanged, until acted upon by users who have the required access to the remaining<br />

quarantines (or until it is released “normally” via early or normal expiration).<br />

System Quarantines and Virus Scanning<br />

Once a message has been released for delivery from all queues in which is has been quarantined, it will<br />

be rescanned for viruses and spam (assuming anti-virus and spam are enabled on that mail policy) before<br />

it can be delivered.<br />

When a message is released from quarantine it is scanned for viruses and spam by the anti-virus and<br />

anti-spam engines (if anti-virus is enabled). If the verdict produced matches the verdict produced the<br />

previous time the message was processed, the message is not re-quarantined. Conversely, if the verdicts<br />

are different, the message could be sent to another quarantine.<br />

The rationale is to prevent messages from looping back to the quarantine indefinitely. For example,<br />

suppose a message is encrypted and therefore sent to the Virus quarantine. If an administrator releases<br />

the message, the anti-virus engine still will not be able to decrypt it; however, the message should not<br />

be re-quarantined or a loop will be created and the message will never be released from the quarantine.<br />

Since the two verdicts are the same, the system bypasses the Virus quarantine the second time.<br />

System Quarantines and Alerts<br />

An alert is sent whenever a quarantine reaches or passes 75% and 95% of its capacity. The check is<br />

performed when a message is placed in the quarantine. So, if adding a message to the Policy quarantine<br />

increases the size to or past 75% of the capacity specified, an alert is sent:<br />

Warning: Quarantine "Policy" is 75% full<br />

For more information about Alerts, see the “System Administration” chapter in the Cisco <strong>IronPort</strong><br />

<strong>AsyncOS</strong> for Email Configuration Guide.<br />

System Quarantines and Logging<br />

<strong>AsyncOS</strong> individually logs all messages that are quarantined:<br />

Info: MID 482 quarantined to "Policy" (message filter:policy_violation)<br />

OL-25138-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!