27.11.2012 Views

IronPort - daily management guide - AsyncOS 7.6.1

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Using the Listener to Test the Appliance<br />

9-16<br />

- admin@ironport.com<br />

Final Message Content:<br />

Received: from remotehost.example.com (HELO TEST) (1.2.3.4)<br />

by stacy.qa with TEST; 19 Oct 2004 00:54:48 -0700<br />

Message-Id: <br />

X-<strong>IronPort</strong>-AV: i="3.86,81,1096873200";<br />

d="scan'208"; a="0:sNHT0"<br />

Subject: hello<br />

This is a test message.<br />

Run through another debug session? [N]><br />

Using the Listener to Test the Appliance<br />

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

Chapter 9 Testing and Troubleshooting<br />

“Black hole” listeners allow you to test your message generation systems, and to also get a rough<br />

measure of receiving performance. Two types of black hole listeners are queueing and non-queueing.<br />

The queueing listener saves the message to the queue, but then immediately deletes it. The non-queueing<br />

listener accepts a message, and then immediately deletes it without saving it.<br />

Use a queuing listener when you are interested in measuring the performance of the entire injection<br />

portion of your message generation system. Use the non-queueing listener when you want to<br />

troubleshoot the connection from your message generation system to the appliance.<br />

For example, in Figure 9-4, you could create a black hole listener “C” to mirror the private listener<br />

labeled “B.” A non-queueing version tests the performance path of the system from the groupware client<br />

to the groupware server to the appliance. A queueing version tests that same path and the appliance’s<br />

ability to enqueue messages and prepare them for delivery via SMTP.<br />

OL-25138-01

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

Saved successfully!

Ooh no, something went wrong!