Cisco Cisco Email Security Appliance C190 用户指南

下载
页码 324
 
7-7
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
After you have entered the values, click Start Trace. A summary of all features configured on the system 
affecting the message is printed.
You can upload message bodies from your local file system. (In the CLI, you can test with message 
bodies you have uploaded to the 
/configuration
 directory. See 
Appendix A, “Accessing the Appliance”
 
for more information on placing files for import onto the Cisco IronPort appliance.)
After the summary is printed, you are prompted to view the resulting message and re-run the test 
message again. If you enter another test message, the Trace page and the 
trace
 command uses any 
previous values from 
 you entered. 
SenderBase 
Network Owner 
Organization ID
Type the unique identification number of the 
SenderBase network owner, or allow the 
system to Lookup network owner ID 
associated with source IP address. 
 
You can view this information if you added 
network owners to sender groups via the 
GUI. 
34
SenderBase 
Reputation 
Score (SBRS 
scores)
Type the SBRS score you want to provide for 
the spoofed domain, or allow the system to 
look up the SBRS score associated with 
source IP address. This can be helpful when 
testing policies that use SBRS scores. Note 
that manually entered SBRS scores are not 
passed to the Context Adaptive Scanning 
Engine (CASE). See “Reputation Filtering” 
in the Cisco IronPort AsyncOS for Email 
Configuration Guide
for more information. 
-7.5
Envelope Sender Type the Envelope Sender of the test 
message. 
admin@example.net
Envelope 
Recipients
Type a list of recipients for the test message. 
Separate multiple entries with commas. 
joe
frank@example.com
Message Body
Type the message body for the test message, 
including headers. Type a period on a 
separate line to end entering the message 
body. Note that “headers” are considered part 
of a message body (separated by a blank 
line), and omitting headers, or including 
poorly formatted ones can cause unexpected 
trace results.
To: 1@example.com
From: ralph
Subject: Test
A test message
.
Table 7-1
 Input for the Trace page  (continued)
Value Description 
Example