SMTP Test 39,40,41

[jess....@gmail.com]

We are seeing issues with SMTP tests 39,40,41. When we click Run, the Logs show an error:

1: Error in TEST MESSAGE BAD DISPOSITION NOTIFICATION: Couldn't connect to host, port: direct.ett.healthit.gov, 25; timeout -1

Is this port closed on your side, or is the issue with us?

[Sandeep Savarala]

Please try again. This issue should be resolved.

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/6d9353f1-bcb9-4352-b10a-f3c0e3f63a29n%40googlegroups.com.

[jess....@gmail.com]

Sandeep, it now appears as if the port is open, but we are not receiving any of the messages.

For example, I just ran SMTP 39, and the Logs showed this:
1: SENDING EMAIL WITH MESSAGE DISPOSITION NOTIFICATION HEADER TO dir...@direct.epic.com 2: Email sent Successfully 3: Message-ID of the email sent: <1245198617.296.1618864731301@localhost>

However, there was no message in our system, nothing for us to generate response MDNs to.

[Sandeep Savarala]

It looks like the tool is not trusting your address  dir...@direct.epic.com. Please reupload your trust anchor and try again.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/fbb2de89-c2ee-429d-9e3d-e3f9f406ba55n%40googlegroups.com.

[jess....@gmail.com]

I am sorry, where am I doing on this on the ETT site?

[jess....@gmail.com]

I'm sorry, is this something we are doing in our system, or in the ETT site? Please let me know.

Thanks.

[Sandeep Savarala]

Upload your trust anchor here.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/0cfbe9dd-b96b-48a7-b02e-26639439e0a9n%40googlegroups.com.

[jess....@gmail.com]

Thank you.

Doing this, and then running SMTP case 39 again, I still do not get any messages in our system.
I ran this case at 9:09 CDT, and the email was "Email sent Successfully 3: Message-ID of the email sent: <1179780493.1224.1619014129217@localhost>"

Is it possible for you to look in to why this is the behavior I see (it says sent, but we don't receive anything)?

Or is there anything else about this test case that changed as part of the weekend maintenance?

[Sandeep Savarala]

Nothing is changed on these tests for at least 2 years. Have you uploaded your new trust anchor?

The ETT is not trusting your address, hence it's not able to send any messages to your system.

We were permanently unable to deliver your message to the following recipients. Please contact your system administrator with further questions.

Failed Recipients:

    dir...@direct.epic.com

Error Message:
The Direct address that you tried to reach is not trusted. Try double-checking the recipient's email address for typos or unnecessary spaces. Learn more by visiting our help. 

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/9e36560b-f2a1-4bb7-aa73-b196f115ccf9n%40googlegroups.com.

[Greg Gurr]

I am seeing the same behavior when we run tests 39, 40 and 41.  We don't receive any emails from the ETT tool.

[jess....@gmail.com]

The ETT's Trust Anchor downloadable from here (https://ett.healthit.gov/ett/#/direct/certdiscovery/dcdt2) appears different from the Trust Anchor downloadable from here (https://ett.healthit.gov/ett/#/direct). Are these Trust Anchors for different purposes?

[Sandeep Savarala]

Yes, the TA seen here  https://ett.healthit.gov/ett/#/direct/certdiscovery/dcdt2   is only used for Direct Certificate Discovery Tool.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/475e8fc5-cf49-4b3c-bda5-19b4faaa97d4n%40googlegroups.com.

[jess....@gmail.com]

Okay, thanks. We are still looking at SMTP 39, 40, and 41. We think we are passing in a valid Trust Anchor for our system..

[jess....@gmail.com]

Sandeep, SMTP Test 39 appears to be working better, but not completely. We are able to get a message into our system from hisp-t...@direct.ett.healthit.gov, but when I click on "Check MDN," it indicates there is no received MDN.

For example, at 9:22-9:23 CDT, I tried. The Logs for the test case returned this:
ERROR: No messages found with Original Message ID: <1007174874.7451.1619187763379@localhost>

However, in our system, for the MDNs we generate, this is what I see (I see the Original Message ID):

Content-Type: multipart/report; report-type="disposition-notification";

 boundary="------------010006080108090007080603"

Message-ID: <976B4A2FFADCA2CF50F320CE3D20A399BD3A5746@DEMO0MU0WEB01>

To: hisp-t...@direct.ett.healthit.gov

From: *************

CKX-Bounce-Address: *********

Date: Fri, 23 Apr 2021 09:22:45 -0500

Subject: processed MDN

MIME-Version: 1.0

--------------010006080108090007080603

Content-Type: text/plain; charset=us-ascii

Content-Transfer-Encoding: 7bit

Your message was successfully processed.

--------------010006080108090007080603

Content-Type: message/disposition-notification

Message-ID: <976B4A2FFADCA2CF50F320CE3D20A399BD3A5746@DEMO0MU0WEB01>

Subject: processed MDN

Reporting-UA: *******; STA

Final-Recipient: rfc822; **********

Original-Message-ID: <1007174874.7451.1619187763379@localhost>

Disposition: automatic-action/MDN-sent-automatically; processed

--------------010006080108090007080603

Content-Type: text/rfc822-headers; charset=windows-1252

Date: Fri, 23 Apr 2021 02:22:43 GMT

Content-Transfer-Encoding: 7bit

X-Priority: 3 (Normal)

MIME-Version: 1.0

X-UserIsAuth: true

Received: from 34.235.25.130 (EHLO localhost) ([34.235.25.130]) by ONCSITE-PROD-DIRECT (JAMES SMTP Server ) with ESMTPA ID 1395360040 for <***********>; Fri, 23 Apr 2021 02:22:43 +0000 (UTC)

Message-ID: <1007174874.7451.1619187763379@localhost>

Content-Type: multipart/mixed; boundary="----=_Part_7450_509481957.1619187763283"

Disposition-Notification-Options: X-DIRECT-FINAL-DESTINATION-DELIVERY=optional,true

Disposition-Notification-To: hisp-t...@direct.ett.healthit.gov

From: hisp-t...@direct.ett.healthit.gov

CKX-Bounce-Address: hisp-t...@direct.ett.healthit.gov

Subject: Testing sending mail with Disposition Notification Header!

To: *************

--------------010006080108090007080603--

[Sandeep Savarala]

I just ran with your address and the test is passing. After you click send email wait for a bit for the MDNs to come back to the tool and click check MDN.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/2f38d06e-226e-4e08-94fa-256f8d16f4b1n%40googlegroups.com.

[jess....@gmail.com]

Spectacular, thank you.

[jess....@gmail.com]

We are now back to the point of not receiving any messages in our system from these three test cases. Once again, we think the trust anchor we are passing in is valid.
Our most recent attempt at SMTP 39 yielded the following information:
1: SENDING EMAIL WITH MESSAGE DISPOSITION NOTIFICATION HEADER TO direct@****.epic.com

2: Email sent Successfully

3: Message-ID of the email sent: <186590462.404.1619460943475@localhost>

I just want to make sure that this is true, that a message is successfully sent.

[jess....@gmail.com]

These cases are now giving me an error, indicating that I can't upload my trust anchor.

[Sandeep Savarala]

Our network team is investigating the Direct issue. I will let you know once it's back up.

To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/4f3dfeec-8364-492a-a127-8e90a04da261n%40googlegroups.com.

[Sandeep Savarala]

This issue is fixed now. Try again.

[jess....@gmail.com]

All functional, thank you.

[Greg Gurr]

We are having issues with SMTP test 41 not sending our system an email (tests 39 and 40 pass).  Was there anything different you had to do to get this test to work?