Руководство Пользователя для Cisco Cisco Content Security Management Appliance M160

You cannot load configurations containing masked passwords. If you anticipate loading 
configurations from the configuration history logs, select Yes to include passwords in the log.

Configure the log retrieval method.

Submit and commit your changes.

Click the name of the log in the Log Name column on the Log Subscriptions page. 

Update the log subscription.

Submit and commit your changes.

The system periodically records system metrics within text mail logs and status logs. Use the Edit 
Settings button in the Global Settings section of the Log Subscriptions page (or the 

logconfig -> setup

 

command in the CLI) to configure:

The amount of time, in seconds, that the system waits between recording metrics

Whether to record the Message ID headers

Whether to record the remote response status code

Whether to record the subject header of the original message

The headers that should be logged for each message

All Cisco Content Security appliance logs optionally include the following three items: 

Message-ID: When this option is configured, every message will have its Message ID header logged, 
if it is available. This Message ID may have come from the received message or may have been 
generated by AsyncOS. For example: 

Tue Apr 6 14:38:34 2004 Info: MID 1 Message-ID Message-ID-Content

Remote Response: When this option is configured, every message will have its remote response 
status code logged, if it is available. For example:

Tue Apr 6 14:38:34 2004 Info: MID 1 RID [0] Response 'queued as 9C8B425DA7'

The remote response string is the human-readable text received after the response to the DATA 
command during the delivery SMTP conversation. In this example, the remote response after the 
connection host issued the data command is “queued as 9C8B425DA7.” 

[...]

250 ok hostname

250 Ok: queued as 9C8B425DA7