Delivery Notification

This test suite verifies a HISP’s compliance with the sending system requirements of the Implementation Guide for Delivery Notification when using the XDR edge protocol. It tests that the sending system can deliver XDR notification messages back to the edge as well as generate failure messages under given failure conditions. In these tests, the testing tool will connect to your HISP using XDR with messages that contain the appropriate headers to invoke the Delivery Notification Guide. Your HISP will convert the XDR messages to SMTP messages with an XDM attachment and send the message to the testing tool’s HISP. Your HISP will then send delivery notification messages back to the testing tool’s XDR endpoint.

TIP

Note: Before you can perform these tests, you must first create an XDR configuration profile with information that tells the testing tool how to connect to your HISP using your XDR server. See the XDR Server Configuration documentation for how to create an XDR configuration profile. If your XDR server requires mutual TLS authentication, you will need to include the testing tool’s XDR client certificate in your XDR server’s store of trusted certificates. You can obtain the testing tool’s XDR client certificate from the Prerequisites section of the testing tool’s home page. The testing tool also provides specific XDR endpoints for this test: one that uses TLS and one that doesn’t; the testing tool does not require any authentication to the XDR endpoints. Before you can perform these tests, you will need to configure the Direct address that you will use in these tests to deliver XDR messages to one of the tool’s XDR endpoints. Be aware that the testing tool’s XDR endpoints are different from the XDR endpoints in the HISP to Edge tests.

Delivery Notification test configuration, showing the Dispatched MDN Delay setting and the two XDR notification endpoints

Workflow

• Navigate to HISP Tools > Edge Protocols > XDR and select the Delivery Notification Test sub-tab under the Edge To HISP tab.
• Select an XDR configuration profile for the XDR server that you would like to test.
• Select a timeout/delay (1–70 minutes). See the note below for more information about the timeout/delay.
• Click Run Tests. The tool immediately begins connecting to your HISP using XDR and sending messages from the configured XDR email account. It monitors the XDR transaction results and looks for XDR notification messages sent from your HISP back to the testing tool’s XDR endpoint. Monitoring continues until the timeout threshold is exceeded.
• Results are displayed in real time as each test scenario completes, with status indicators for running, success, failed, and aborted.

Test scenarios running in real time

• Once all scenarios finish, the overall suite status is shown (SUCCESS, FAILED, or ABORTED).
• The tool generates a report indicating success or failure and lists any scenarios that failed. The results can be viewed in the Results and Reports section of the tool under Management > Results and Reports.

Completed test suite showing overall SUCCESS status

Note: Some of the scenarios expect that a DSN notification message will be generated in response to a timeout event caused by the sending HISP not receiving the expected MDN messages within a given amount of time. In most HISPs, this timeout is 60 minutes. In one particular scenario, the test validates that a DSN message is generated by the sending HISP due to a timeout, but the receiving HISP then sends a dispatched MDN after the timeout. The Dispatched MDN Delay timeout tells the receiving HISP how long it should wait before it tries to send the dispatched MDN. To correctly set the Dispatched MDN Delay timeout, you should make it at least 1 minute longer than your HISP’s timeout threshold for waiting for notification messages. The testing tool will wait an additional 5 minutes on top of the Dispatched MDN Delay before it completes the test (when using a non-manual-retrieval edge protocol).

If the testing tool successfully receives an XDR notification message from your HISP at the testing tool’s XDR endpoint, you can view the received XDR notification message by clicking the “View Notification Message” link for each test scenario. The viewer shows the full XDR notification in the “XDR Notification Message” text box, and shows the disposition content embedded in the notification message in the “Message Disposition Content” text box. The disposition content should be the contents of the document embedded in the notification message.

Test Scenarios

Each test maps to a specific payload-to-XDR notification messaging scenario. The following table lists all tests and the scenario they cover:

Test Name	Scenario Description
ExceptionPathNoProcessedMDN	The testing tool connects to the XDR server and attempts to send a message to a destination that does not return a processed MDN. The sending HISP detects the error condition after the timeout threshold has been exceeded and generates a DSN message. The DSN message is converted into an XDR notification message with a failure disposition and sent to the testing tool’s XDR endpoint. The testing tool expects to receive a single XDR failure notification message from your HISP that corresponds to the original message.
ExceptionPathNoPublishedCertificate	The testing tool connects to the XDR server and attempts to send a message to a destination that does not have a published certificate. The sending HISP detects the error condition and generates a DSN message that is sent back to the sender. The DSN message is converted into an XDR notification message with a failure disposition and sent to the testing tool’s XDR endpoint. The testing tool expects to receive a single XDR failure notification message from your HISP that corresponds to the original message.
ExceptionPathUntrusted	The testing tool connects to the XDR server and attempts to send a message to a destination that is not trusted by the sending HISP. The sending HISP detects the error condition and generates a DSN message that is sent back to the sender. The DSN message is converted into an XDR notification message with a failure disposition and sent to the testing tool’s XDR endpoint. The testing tool expects to receive a single XDR failure notification message from your HISP that corresponds to the original message.
HappyPathGoodRequest	The testing tool connects to the XDR server and attempts to send a message to a destination that successfully delivers the message to its final destination. The sending HISP adds the appropriate headers to the generated SMTP message that invoke the Delivery Notification Guide. The receiving system generates a dispatched MDN message and sends it back to the sending HISP. The dispatched MDN message received by your (sending) HISP is converted into an XDR notification message with a success disposition and sent to the testing tool’s XDR endpoint. The testing tool expects to receive a single XDR success notification message from your HISP that corresponds to the original message.