The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The System Status page on your Cisco Email Security Appliance (ESA) has a variety of counters, rates, and gauges that can be used both to monitor the health of the appliance and understand your mail stream.
This page can be access from the GUI via Monitor>System Status
From CLI a similar view can be found using the status detail command:
esa.example.com> status detail
Status as of: Wed Aug 06 08:24:18 2014 EDT
Up since: Wed Jul 09 15:10:21 2014 EDT
(27d 17h 13m 57s)
Last counter reset: Wed Jul 23 14:21:11 2014 EDT
System status: Online
Oldest Message: 1 day 17 hours 10 mins 37 secs
Feature - Symantec Brightmail Anti-Spam: Expired
Feature - IronPort Image Analysis: Expired
Feature - Sophos Anti-Virus: 232 days
Feature - Bounce Verification: Perpetual
Feature - IronPort Anti-Spam: 232 days
Feature - IronPort Email Encryption: 232 days
Feature - RSA Email Data Loss Prevention: 232 days
Feature - Intelligent Multi-Scan: 68 days
Feature - Incoming Mail Handling: Perpetual
Feature - Outbreak Filters: 232 days
The "Oldest Message" value indicates the amount of time that the oldest message has been awaiting delivery. This includes messages that are in both the Work Queue or in the Message Queue. The unattempted recipients value is a subset of active recipients in the message queue and can therefore include the oldest message.
The Oldest Message should not be older than "the maximum number of seconds a message may stay in the queue before being hard bounced," as configured via the bounceconfig command in the CLI, or Network->Bounce Profiles in the GUI.