Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 324
 
5-42
Cisco IronPort AsyncOS 7.6 for Email Daily Management Guide
OL-25138-01
Chapter 5      Logging
Log Subscriptions
Step 2
Make changes to the log subscription.
Step 3
Submit and commit your changes.
Configuring Global Settings for Logging
The system periodically records system measurements within the IronPort Text Mail Logs and the 
IronPort Status Logs. Use the Edit Settings button in the Global Settings section of the System 
Administration > Log Subscriptions page (or the 
logconfig -> setup
 command in the CLI) to 
configure:
  •
System metrics frequency. This is the amount of time, in seconds, that the system waits between 
recording measurements.
  •
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.
  •
A list of headers that should be logged for each message.
All IronPort logs optionally include the following three pieces of data: 
1.
Message-ID 
When this option is configured, every message will have its Message ID header logged, if it is 
available. Note that this Message-ID may have come from the received message or may have been 
generated by AsyncOS itself. For example: 
2.
Remote Response 
When this option is configured, every message will have its remote response status code logged, if 
it is available. For example:
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.” 
Whitespace, punctuation, (and in the case of the 250 response, the OK characters) are stripped from 
the beginning of the string. Only whitespace is stripped from the end of the string. For example, 
Cisco IronPort appliances, by default, respond to the DATA command with this string: 250 Ok: 
Message MID accepted. So, the string “Message MID accepted” would be logged if the remote host 
were another Cisco IronPort appliance. 
3.
Original Subject Header
Tue Apr 6 14:38:34 2004 Info: MID 1 Message-ID Message-ID-Content
Tue Apr 6 14:38:34 2004 Info: MID 1 RID [0] Response 'queued as 9C8B425DA7'
[...]
250 ok hostname
250 Ok: queued as 9C8B425DA7