Cisco Cisco Email Security Appliance C190 Technical References

- ALERT_TIMEOUT - Configure when you will be alerted due to failing to get reporting data

- DOMAIN - Configure domain report settings.

- MODE - Enable/disable centralized reporting.

[]>

mail3.example.com> reportingconfig

Choose the operation you want to perform:

- MAILSETUP - Configure reporting for the ESA.

- MODE - Enable centralized or local reporting for the ESA.

[]> mode

Centralized reporting: Local reporting only.

Do you want to enable centralized reporting? [N]> y

Choose the operation you want to perform:

- MAILSETUP - Configure reporting for the ESA.

- MODE - Enable centralized or local reporting for the ESA.

[]>

mail.example.com> reportingconfig

Choose the operation you want to perform:

- MAILSETUP - Configure reporting for the ESA.

- MODE - Enable centralized or local reporting for the ESA.

[]> mailsetup

SenderBase timeout used by the web interface: 5 seconds

Sender Reputation Multiplier: 3

The current level of reporting data recording is: unlimited

No custom second level domains are defined.

Legacy mailflow report: Disabled

Choose the operation you want to perform:

- SENDERBASE - Configure SenderBase timeout for the web interface.

- MULTIPLIER - Configure Sender Reputation Multiplier.

- COUNTERS - Limit counters recorded by the reporting system.

- THROTTLING - Limit unique hosts tracked for rejected connection reporting.

- TLD - Add customer specific domains for reporting rollup.

- STORAGE - How long centralized reporting data will be stored on the C-series before 

being overwritten.

- LEGACY - Configure legacy mailflow report.

[]> storage

While in centralized mode the C-series will store reporting data for the M-series to 

collect.  If the M-series does not collect that data then eventually the C-series will 

begin to overwrite the oldest data with new data.

A maximum of 24 hours of reporting data will be stored.

How many hours of reporting data should be stored before data loss?