Our technical team is actively assisting clients in resolving issues with encrypted SMTP emails. Based on my understanding of the mechanism:
- "SMTP Test 8, 14, 18 (Send)" is designed to verify the sending system's ability to transmit emails to the ETT endpoint using the SMTP protocol, STARTTLS, and PLAIN SASL authentication (if enabled).
- Following the documented steps, we created a new message and sent it to the ETT endpoint recipient, wellf...@ett.healthit.gov.
- Upon leaving our direct server, the message should be encrypted using the public certificate of wellf...@ett.healthit.gov, then delivered to the recipient's mail server (identified via NS record as ec2-34-235-25-130.compute-1.amazonaws.com).
- The recipient server should decrypt the message using the private key associated with wellf...@ett.healthit.gov and place it in the inbox.
- The ETT tool is then expected to analyze the message, providing test result details (e.g., constraints, conformance, contributing factors for Pass/Fail outcomes) as part of the testing artifact.
- According to the user guide, the Validation Report aggregates all tests from a session, enabling users to view results by profile and executed test cases. It is assumed that the tool scans decrypted messages in plaintext format during this process.
I noticed a discrepancy between previous and current tool behavior. A screenshot from September 17, 2024, displayed raw messages with extracted key header elements like
Subject and
Content-Type. However, the current tool appears to generate reports using encrypted messages.
Could you confirm if there have been any updates to the ETT tool since then?
Please let me know if additional details are needed. Thanks.