Cisco Cisco Email Security Appliance C160 Mode D'Emploi

contains the Anti-Spam section that lists the Anti-Spam pages. Accordingly, when referring to specific 
pages in the GUI, the documentation uses the menu name, followed by an arrow and then the page name. 
For example, Security Services > SenderBase.

The Monitor section contain pages for the Mail Flow Monitor feature (Overview, Incoming Mail, 
Outgoing Destinations, Outgoing Senders, Delivery Status, Internal Users, Content Filters, Virus 
Outbreaks, Virus Types, System Capacity, System Status), Local and External Quarantines, and 
Scheduled Reports features. You can also access message tracking from this menu.

The Mail Policies section contains pages for the Email Security Manager feature (including Mail 
Policies and Content Filters), the Host Access Table (HAT) and Recipient Access Table (RAT) 
configuration, Destination Controls, Bounce Verification, Domain Keys, Text Resources, and 
Dictionaries. 

The Security Services section contains pages to set global settings for the Anti-Spam, Anti-Virus, Cisco 
IronPort Email Encryption, Outbreak Filters, and SenderBase Network Participation features. You also 
enable the following features from this menu: Reporting, Message Tracking, External Spam Quarantine.

The Network section contains pages for creating and managing IP interfaces, Listeners, SMTP Routes, 
DNS, Routing, Bounce Profiles, SMTP Authentication, and Incoming Relays. 

The System Administration section contains pages for the Trace, Alerting, User Management, LDAP, 
Log Subscription, Return Addresses, System Time, Configuration File management, Feature Key 
Settings, Feature Keys, Shutdown/Reboot, Upgrades, and System Setup Wizard features.

If you have the Centralized Management feature and have enabled a cluster, you can browse machines 
in the cluster, create, delete, copy, and move settings among clusters, groups, and machines (that is, 
perform the equivalent of the 

clustermode

 and 

clusterset

 commands) from within the GUI. 

For more information, see “Administering a Cluster from the GUI” in the Cisco IronPort AsyncOS for 
Email Advanced Configuration Guide. 

The commit model in the GUI matches the same “explicit commit” model as used in the CLI. (For more 
information, see 

.) As you make configuration changes in 

the GUI, you now must explicitly commit those changes by clicking the Commit Changes button. This 
button displays when you have uncommitted changes that need to be saved.