27.11.2012 Views

IronPort - daily management guide - AsyncOS 7.6.1

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 7 Other Tasks in the GUI<br />

OL-25138-01<br />

Table 7-1 Input for the Trace page (continued)<br />

Value Description Example<br />

SenderBase<br />

Network Owner<br />

Organization ID<br />

SenderBase<br />

Reputation<br />

Score (SBRS<br />

scores)<br />

Type the unique identification number of the<br />

SenderBase network owner, or allow the<br />

system to Lookup network owner ID<br />

associated with source IP address.<br />

You can view this information if you added<br />

network owners to sender groups via the<br />

GUI.<br />

Type the SBRS score you want to provide for<br />

the spoofed domain, or allow the system to<br />

look up the SBRS score associated with<br />

source IP address. This can be helpful when<br />

testing policies that use SBRS scores. Note<br />

that manually entered SBRS scores are not<br />

passed to the Context Adaptive Scanning<br />

Engine (CASE). See “Reputation Filtering”<br />

in the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for Email<br />

Configuration Guidefor more information.<br />

Envelope Sender Type the Envelope Sender of the test<br />

message.<br />

Envelope<br />

Recipients<br />

Type a list of recipients for the test message.<br />

Separate multiple entries with commas.<br />

Message Body Type the message body for the test message,<br />

including headers. Type a period on a<br />

separate line to end entering the message<br />

body. Note that “headers” are considered part<br />

of a message body (separated by a blank<br />

line), and omitting headers, or including<br />

poorly formatted ones can cause unexpected<br />

trace results.<br />

Debugging Mail Flow Using Test Messages: Trace<br />

After you have entered the values, click Start Trace. A summary of all features configured on the system<br />

affecting the message is printed.<br />

You can upload message bodies from your local file system. (In the CLI, you can test with message<br />

bodies you have uploaded to the /configuration directory. See Appendix A, “Accessing the Appliance”<br />

for more information on placing files for import onto the Cisco <strong>IronPort</strong> appliance.)<br />

After the summary is printed, you are prompted to view the resulting message and re-run the test<br />

message again. If you enter another test message, the Trace page and the trace command uses any<br />

previous values from Table 7-1 you entered.<br />

Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email Daily Management Guide<br />

34<br />

-7.5<br />

admin@example.net<br />

joe<br />

frank@example.com<br />

To: 1@example.com<br />

From: ralph<br />

Subject: Test<br />

A test message<br />

.<br />

7-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!