Cisco Cisco Email Security Appliance X1050 Guía Del Usuario
7-6
Cisco IronPort AsyncOS 7.6 for Email Daily Management Guide
OL-25138-01
Chapter 7 Other Tasks in the GUI
Debugging Mail Flow Using Test Messages: Trace
–
View a subset of key statistics.
•
The System Status page provides a detailed representation of all real-time mail and DNS activity
for the system. You can also reset the counters for system statistics and view the last time the
counters were reset.
for the system. You can also reset the counters for system statistics and view the last time the
counters were reset.
•
On the System Trace page, you can debug the flow of messages through the system by emulating
sending a test message. You can emulate a message as being accepted by a listener and print a
summary of features that would have been “triggered” or affected by the current configuration of the
system.
sending a test message. You can emulate a message as being accepted by a listener and print a
summary of features that would have been “triggered” or affected by the current configuration of the
system.
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
(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 (including
uncommitted changes) of the system. The test message is not actually sent. The Trace page (and
uncommitted changes) 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.
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 7-1
Input for the Trace page
Value
Description
Example
Source IP
address
address
Type the IP address of the remote client to
mimic the source of the remote domain. This
can be an Internet Protocol version 4 (IPv4)
or version 6 (IPv6) address.
mimic the source of the remote domain. This
can be an Internet Protocol version 4 (IPv4)
or version 6 (IPv6) address.
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
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.
blank, so it is impossible to test a scenario
where the DNS does not reverse match
properly.
203.45.98.109
2001:0db8:85a3::8a2e:0370:7334
Fully Qualified
Domain Name
of the Source IP
Domain Name
of the Source IP
Type the fully-qualified remote domain name
to mimic. If left null, a reverse DNS lookup
will be performed on the source IP address.
to mimic. If left null, a reverse DNS lookup
will be performed on the source IP address.
smtp.example.com
Listener to Trace
Behavior on
Behavior on
Choose from the list of listeners configured
on the system to emulate sending the test
message to.
on the system to emulate sending the test
message to.
InboundMail