SMTP MT Test 39 shows success but no Delivery Notification is actually sent

63 views
Skip to first unread message

Pranav Kulkarni

unread,
Feb 3, 2026, 1:02:09 AM (5 days ago) Feb 3
to Edge Test Tool (ETT)

Hi Team,

I’m facing an issue with SMTP MT Test 39 (Message with Good Header) under H1 – Delivery Notifications.

Issue Summary

The Edge Test Tool reports successful delivery, but no Delivery Notification (MDN) is actually sent or received by our SMTP server.

Observed Behavior
  • Test log shows:

    1: SENDING EMAIL WITH MESSAGE DISPOSITION NOTIFICATION HEADER 2: Email sent Successfully 3: Message-ID of the email sent: <…@localhost>
  • However:

    • No inbound SMTP connection is observed on our server

    • No message appears in the James SMTP logs

    • No message is delivered to the local mailbox

Unexpected Behavior

Even when:

  • The SMTP host does not exist

  • The username does not exist

  • Invalid credentials are provided

👉 The test still reports “Email sent Successfully”.

This makes it difficult to determine whether:

  • The tool is actually attempting SMTP delivery, or

  • The tool is short-circuiting the test and marking it as success without real SMTP transmission.

Verification Done on Our Side
  • Manual SMTP delivery via telnet works correctly

  • Domain and mailbox exist and are local

  • TLS and certificates are configured

  • Inbound SMTP traffic is verified

  • No SMTP traffic is received from ETT during this test

Question / Clarification Needed
  1. Does SMTP MT Test 39 perform real SMTP delivery, or is it a simulated send?

  2. How does ETT determine “Email sent Successfully” for this test?

  3. Should the tool fail when:

    • SMTP host is unreachable?

    • Username/password are invalid?

  4. Is there a way to force real SMTP delivery and validate MDN receipt?

Any guidance or clarification would be greatly appreciated, as this behavior blocks proper validation of Delivery Notification handling.

Thanks in advance for your support.

Screenshot from 2026-02-03 11-26-36.png

Pranav Kulkarni

unread,
Feb 3, 2026, 1:50:01 AM (5 days ago) Feb 3
to Edge Test Tool (ETT)
Credentials -
Host Name - mail.fhir.spryhealth.care
Email - fh...@fhir.spryhealth.care

Sai Valluripalli

unread,
Feb 3, 2026, 7:14:58 AM (5 days ago) Feb 3
to Pranav Kulkarni, Edge Test Tool (ETT)
Can you try again today and let us know

--
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 visit https://groups.google.com/d/msgid/edge-test-tool/0e9dfc99-28af-44bf-97bd-5744768f3597n%40googlegroups.com.

Pranav Kulkarni

unread,
Feb 4, 2026, 1:53:51 AM (4 days ago) Feb 4
to Edge Test Tool (ETT)

Hi Sai,

I checked again yesterday and one message was received once without any configuration change, which confirms that our SMTP setup is capable of receiving the MDN.

However, today the issue has reverted to the same behavior described above:

  • Test still reports “Email sent Successfully”

  • No inbound SMTP connection is observed

  • No message appears in James SMTP logs

  • No message is delivered to the local mailbox

    This inconsistency makes the tool behavior appear unstable or non-deterministic, as the same configuration once results in a received message and now results in no SMTP delivery at all.

    We have an official test scheduled tomorrow, and this is currently blocking our ability to validate H1 Delivery Notification (MDN) handling.

    Any guidance or update would be greatly appreciated, as this is time-sensitive for our upcoming test.

    Thanks in advance for your support.

    Best regards,
    Pranav Kulkarni

    image (1).png

    Facundo Jesus Gomez Algazán

    unread,
    Feb 4, 2026, 10:17:07 AM (4 days ago) Feb 4
    to Edge Test Tool (ETT)
    Hello,

    Looks like this is still happening for me, logs shows:
    Screenshot 2026-02-04 at 12.15.59 PM.png
    But I don't see any activity on my server. 

    Can this be fixed ASAP?

    Thank you
    Reply all
    Reply to author
    Forward
    0 new messages