Cisco Cisco Email Security Appliance C390 ユーザーガイド

ページ / 418
5-157
Cisco IronPort AsyncOS 7.3 for Email Daily Management Guide
OL-23080-01
Chapter 5      Logging
Overview
Delivery Logs
Delivery logs record critical information about the email 
delivery operations of the IronPort appliance — for 
example, information regarding each recipient delivery and 
bounce at the time of the delivery attempt. The log 
messages are “stateless,” meaning that all associated 
information is recorded in each log message and users need 
not reference previous log messages for information about 
the current delivery attempt. Delivery logs are recorded in a 
binary format for resource efficiency. Delivery Log files 
must be post-processed using a provided utility to convert 
them to XML or CSV (comma-separated values) format. 
The conversion tools are located at:
 
http://support.ironport.com
Bounce Logs
Bounce logs record information about bounced recipients. 
The information recorded for each bounced recipient 
includes: the message ID, the recipient ID, the Envelope 
From address, the Envelope To address, the reason for the 
recipient bounce, and the response code from the recipient 
host. In addition, you can choose to log a fixed amount of 
each bounced recipient message. This amount is defined in 
bytes and the default is zero.
Status Logs
This log file records system statistics found in the CLI 
status commands, including 
status detail
 and 
dnsstatus
The period of recording is set using the 
setup
 subcommand 
in 
logconfig
. Each counter or rate reported in status logs is 
the value since the last time the counter was reset.
Domain Debug Logs
Domain debug logs record the client and server 
communication during an SMTP conversation between the 
Cisco IronPort appliance and a specified recipient host. 
This log type can be used to debug issues with specific 
recipient hosts. You must specify the total number of SMTP 
sessions to record in the log file. As sessions are recorded, 
this number decreases. You can stop domain debug before 
all sessions have been recorded by deleting or editing the 
log subscription.
Table 5-1
Log Types (continued)
Log
Description