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 />

Ensuring that End Users Receive the Notifications<br />

Receiving Multiple Notifications<br />

OL-25138-01<br />

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

Consider recommending that end users add the From: address for the Cisco <strong>IronPort</strong> Spam Quarantine<br />

notification emails to the “whitelist” in their Mail application’s (Outlook, Thunderbird, etc.) Junk Mail<br />

Settings.<br />

Users belonging to multiple email aliases or using several email addresses will receive multiple<br />

notifications. This is also the case for users belonging to LDAP groups receiving email.<br />

Table 4-4 Notifications per Address/Alias<br />

User Email Addresses Aliases Notifications<br />

Sam sam@example.com 1<br />

Mary mary@example.com dev@example.com,<br />

qa@example.com,<br />

4<br />

Joe joe@example.com,<br />

admin@example.com<br />

Note If you do not use LDAP and you do not want your end users to receive multiple email notifications,<br />

consider disabling notifications and instead allow end users to access the quarantine directly and<br />

authenticate via LDAP or POP/IMAP.<br />

Determining Which Messages are Present for Each User<br />

Depending on the method of authentication (LDAP or IMAP/POP) users may see mail for multiple email<br />

address in the Cisco <strong>IronPort</strong> Spam quarantine.<br />

When using LDAP authentication, if the Primary Email attribute has multiple values in the LDAP<br />

directory, all of those values (addresses) will be associated with the user. Therefore, quarantined<br />

messages addressed to all email addresses associated with the end user in the LDAP directory are present<br />

in the quarantine.<br />

If, however, the user accesses the quarantine directly via a notification, or if the authentication method<br />

is IMAP/POP, the quarantine will only display messages for that user’s email address (or the address to<br />

which the notification was sent). For more information about how end user authentication works, see<br />

End Users Accessing the Cisco <strong>IronPort</strong> Spam Quarantine, page 4-31.<br />

Keep in mind that email addresses are case insensitive in the Cisco <strong>IronPort</strong> Spam Quarantine, so for<br />

example, email for Admin@example.com and admin@example.com will both be present in the<br />

quarantine for a user associated with “admin@example.com.”<br />

Limiting which Addresses have Mail Quarantined<br />

pm@example.com<br />

hr@example.com 3<br />

You can use multiple mail policies (Mail Policies > Incoming Mail Policy) to specify a list of recipient<br />

addresses for which mail will not be quarantined. Select ‘Deliver’ or ‘Drop’ instead of quarantine when<br />

configuring the anti-spam settings for the mail policy.<br />

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

4-33

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

Saved successfully!

Ooh no, something went wrong!