SMTP Test 8, 14, 18 not working 9/15/25 - no login methods supported

17 views
Skip to first unread message

lcm...@emrdirect.com

unread,
Sep 15, 2025, 1:43:36 PM (4 days ago) Sep 15
to Edge Test Tool (ETT)
 Hello,
This test was working as expected last week. The associated SUT setup and ETT testing profile values have not been changed since that time.

After clicking the RUN button the test fails immediately with the following displayed in the test logs:

Test Logs

ERROR: Cannot fetch email from :No login methods supported!

Waiting for >30 seconds is not the issue. The same error appears upon clicking the refresh button for this test. We can confirm from SUT SMTP logs that the SASL authentication is working correctly and that the messages are being accepted by the james server; the james server returns "250 2.6.0 Message received" as expected.

This is a different error from the errors we've reported in other threads over the past few months 

Thank you for your attention to this issue.
Luis Maas, CTO, EMR Direct

lcm...@emrdirect.com

unread,
Sep 18, 2025, 6:57:40 PM (14 hours ago) Sep 18
to Edge Test Tool (ETT)
Hello, the behavior of SMTP Test 8, 14, 18 changed on 9/16/25. 

The james server is no longer accepting the messages.
It appears that changes have been made on the ETT side to the recipient address validation.
The SMTP session fails as follows. I've redacted the b.1 test address below but it is one we have used successfully for a while.

STARTTLS succeeds
SASL authentication succeeds - we are using the credentials list in the More Info window.
235 Authentication Successful
MAIL FROM:<{address redacted}>
250 2.1.0 Sender <{address redacted}> OK
503 5.7.1 Incorrect Authentication for Specified Email Address

The 503 error is new since Monday. We are using the SASL authentication specified for this test so this error suggest a misconfiguration of the validation logic in the james server.
The SMTP session is aborted at this point since the recipient cannot be specified.

As before, your attention to this issue is appreciated as we have customers with pending certification testing that are depending on this test being fixed so they can complete their testing.

Thank you,
Luis Maas, CTO, EMR Direct
Reply all
Reply to author
Forward
0 new messages