27.11.2012 Views

IronPort - daily management guide - AsyncOS 7.6.1

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 4 Quarantines<br />

Disk Space<br />

OL-25138-01<br />

Configuring the Cisco <strong>IronPort</strong> Spam Quarantines Feature<br />

Table 4-3 shows the amount of disk space available on each appliance for the Cisco <strong>IronPort</strong> Spam<br />

Quarantine.<br />

Table 4-3 Disk Space Available for Cisco <strong>IronPort</strong> Spam Quarantine by Cisco <strong>IronPort</strong> Appliance<br />

End Users Accessing the Cisco <strong>IronPort</strong> Spam Quarantine<br />

LDAP Authentication<br />

Model Disk Space (in GBytes)<br />

C150/160 5<br />

C350/360/370 15<br />

C650/660/670 30<br />

X1050/1060/1070 30<br />

End users can access the Cisco <strong>IronPort</strong> Spam quarantine via a link in the notification they receive. When<br />

accessing the quarantine via this method, LDAP or IMAP/POP authentication is not required (end users<br />

do not have to authenticate themselves). Note that the links present in the notification messages do not<br />

expire, so end users can use these links to view their quarantined messages without having to<br />

authenticate.<br />

Users can also access the quarantine by entering a link in their web browser directly. When accessing<br />

the quarantine via a URL typed into a web browser, users will have to authenticate. The authentication<br />

method — LDAP or “mailbox” (IMAP/POP) — is defined in the End User Quarantine Access section<br />

of the quarantine settings (see Configuring End User Quarantine Access, page 4-24).<br />

The authentication process for LDAP works like this:<br />

Step 1 A user enters their username and password into the web UI login page.<br />

Step 2 The Cisco <strong>IronPort</strong> Spam quarantine connects to the specified LDAP server either to perform an<br />

anonymous search or as an authenticated user with the specified “Server Login” DN and password. For<br />

Active Directory, you will usually need to have the server connect on the “Global Catalog port” (it is in<br />

the 6000s) and you need to create a low privilege LDAP user that the Cisco <strong>IronPort</strong> Spam quarantine<br />

can bind as in order to execute the search.<br />

Step 3 The Cisco <strong>IronPort</strong> Spam quarantine then searches for the user using the specified BaseDN and Query<br />

String. When a user’s LDAP record is found, the Cisco <strong>IronPort</strong> Spam quarantine then extracts the DN<br />

for that record and attempts bind to the directory using the user records’ DN and the password they<br />

entered originally. If this password check succeeds then the user is properly authenticated, but the Cisco<br />

<strong>IronPort</strong> Spam quarantine still needs to determine which mailboxes’ contents to show for that user.<br />

Step 4 Messages are stored in the Cisco <strong>IronPort</strong> Spam quarantine using the recipient's envelope address. After<br />

a user's password is validated against LDAP, the Cisco <strong>IronPort</strong> Spam quarantine then retrieves the<br />

“Primary Email Attribute” from the LDAP record to determine which envelope address they should show<br />

quarantined messages for. The “Primary Email Attribute” can contain multiple email addresses which<br />

are then used to determine what envelope addresses should be displayed from the quarantine for the<br />

authenticated user.<br />

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

4-31

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

Saved successfully!

Ooh no, something went wrong!