Cisco Cisco Email Security Appliance C690 User Guide

Page of 456
Chapter 9      Testing and Troubleshooting
Debugging Mail Flow Using Test Messages: Trace
9-2
Cisco IronPort AsyncOS 7.5 for Email Daily Management Guide
OL-25138-01
Debugging Mail Flow Using Test Messages: Trace
You can use System Administration > Trace page (the equivalent of the 
trace
 
command in the CLI) to debug the flow of messages through the system by 
emulating sending a test message. The Trace page (and 
trace
 CLI command) 
emulates a message as being accepted by a listener and prints a summary of 
features that would have been “triggered” or affected by the current configuration 
of the system. The test message is not actually sent. The Trace page (and 
trace
 
CLI command) can be a powerful troubleshooting or debugging tool, especially if 
you have combined many of the advanced features available on the Cisco IronPort 
appliance. 
The Trace page (and 
trace
 CLI command) prompts you for the input parameters 
listed in 
Table 9-1
 Input for the Trace page 
Value 
Description 
Example
Source IP 
address
Type the IP address of the remote client to 
mimic the source of the remote domain.
Note: The 
trace
 command prompts for an 
IP address and a fully-qualified domain 
name. It does not attempt to reverse the IP 
address to see if it matches the 
fully-qualified domain name. The 
trace
 
command does not allow the 
fully-qualified domain name field to be 
blank, so it is impossible to test a scenario 
where the DNS does not reverse match 
properly. 
203.45.98.109
Fully 
Qualified 
Domain 
Name of the 
Source IP
Type the fully-qualified remote domain 
name to mimic. 
smtp.example.com
Listener to 
Trace 
Behavior on
Choose from the list of listeners 
configured on the system to emulate 
sending the test message to. 
InboundMail