Cisco Cisco Email Security Appliance C170 사용자 가이드

다운로드
페이지 324
 
2-32
Cisco IronPort AsyncOS 7.6 for Email Daily Management Guide
OL-25138-01
Chapter 2      Using Email Security Monitor
Email Security Monitor Pages
from an individual sender, based on the mail-from address. The Rate Limits report allows you to quickly 
identify individual senders of large numbers of messages. Use this report to help you to: 
  •
Control spam from internal user accounts, for example in cases when a user's credentials are 
compromised and the account is used to send spam in bulk. 
  •
Identify compromised user accounts. 
  •
Limit out-of-control applications that use email for notifications, alerts, automated statements, etc.
  •
Avoid damaging your organization’s online reputation and the attendant hassles resulting from this 
situation 
Rate Limiting is configured in Mail Policies > Mail Flow Policies. For more information on rate limiting, 
see the “Configuring the Gateway to Receive Email” chapter in the AsyncOS for Email Configuration 
Guide
Figure 2-30
Rate Limits Page 
The System Capacity Page
The System Capacity page provides a detailed representation of the system load, including messages in 
the work queue, average time spent in the work queue, incoming and outgoing messages (volume, size, 
and number), overall CPU usage, CPU usage by function, and memory page swapping information. 
The system capacity page can be used to determine the following information:
  •
Identify when a Cisco IronPort appliance is exceeding recommended capacity and configuration 
optimization or additional appliances are needed. 
  •
Identify historical trends in system behavior which point to upcoming capacity issues. 
  •
Identify which part of the system is using the most resources to assist with troubleshooting. 
It is important to monitor your Cisco IronPort appliance to ensure that your capacity is appropriate to 
your message volumes. Over time, volume will inevitably rise and appropriate monitoring will ensure 
that additional capacity or configuration changes can be applied proactively. The most effective way to 
monitor system capacity is to track overall volume, messages in the work queue and incidents of 
Resource Conservation Mode.