What works Direct SMTP send from Windows (same host/port/username/password/From) succeeds; message is accepted and delivered.
What OME reports API shows credentials are present:
- `UseCredentials: true` - `User: <smtp-username>` - After POST, `Password: null` (hidden/stored)
But test task fails with:
javax.mail.AuthenticationFailedException: failed to connect, no user name specified? at javax.mail.Service.connect(...) at ...EmailClient.sendEmailMessage(EmailClient.java:282) at ...TestSmtpConfigSubTask.sendMail(...)
Appliance DNS resolution of the SMTP hostname succeeds before the failure.
Steps already tried - Re-entered SMTP credentials in UI - Updated SMTP config via REST API - Set SMTP timeout - Restarted services via TUI
Failure remains the same.
Conclusion Looks like OME stores the SMTP username but does not pass it into the JavaMail session. This does not appear to be an SMTP provider or network issue.
Questions 1. Known issue on 4.7.0 with authenticated SMTP/STARTTLS? 2. Supported way to force credential reload so `EmailClient` gets the username? 3. Recommended workaround besides an internal unauthenticated SMTP relay?
Based on the information reviewed, this does not appear to be a domain-related issue.
The error reported by OpenManage Enterprise 4.7.0 is:
AuthenticationFailedException: failed to connect, no user name specified
DNS resolution and SMTP connectivity appear to be functioning correctly, and the same SMTP credentials work successfully outside of OME. This suggests that the issue is more likely related to how OME 4.7.0 handles authenticated SMTP/STARTTLS sessions rather than a problem with the domain configuration itself.
Further investigation will require log collection and analysis. As a next step, please use the Dell Community Direct Message (DM) link below to share the requested information:
Please collect and share the OME logs for deeper troubleshooting. Based on the findings, Dell may recommend either rolling back to a previous OME version or waiting for a future OME release if the issue is confirmed to be software-related.
Additionally, could you please share the Service Tag of the system where OME is being used? Kindly provide it via Direct Message using the link above.
Dell-Ravi C
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
If the credential reload sequence does not bypass the serialization bug, implement one of these two architectural workarounds:
Leverage a Local Containerized Proxy Relay: Spin up a lightweight local postfix or stunnel proxy container on your virtualization infrastructure. Configure the container to listen locally on port 25 without authentication, while it handles the outward authenticated STARTTLS mapping to port 587 on your public submission endpoint. Map OME to this local anonymous destination.
Downgrade to Port 25 with IP-Based Whitelisting: If your public submission endpoint supports it, bypass implicit authentication requirements entirely by creating an explicit inbound IP address allowlist policy rule directly on your mail server firewall / exchange gateway, allowing OME to transmit alerts anonymously across port 25.
with kind regards Martin/ Liebe Grüße Martin
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!
I would recommend either rolling back to the previous version or waiting for version 4.8, which is expected to be released in the future. Unfortunately, I do not have an exact release date that I can share at this time.
If you would like us to investigate the issue further, you can open a software support case with our team through the hotline.
Instructions for collecting the required logs can be found here:
Dell-Ravi C
Moderator
•
25 Posts
•
77 Points
3
0
Posted September 9th, 2026 03:00
Hi domdain,
Based on the information reviewed, this does not appear to be a domain-related issue.
The error reported by OpenManage Enterprise 4.7.0 is:
DNS resolution and SMTP connectivity appear to be functioning correctly, and the same SMTP credentials work successfully outside of OME. This suggests that the issue is more likely related to how OME 4.7.0 handles authenticated SMTP/STARTTLS sessions rather than a problem with the domain configuration itself.
Further investigation will require log collection and analysis. As a next step, please use the Dell Community Direct Message (DM) link below to share the requested information:
https://www.dell.com/community/en/direct-messaging?entityId=C_6a57404a3fe8a237e9f53eb4&entityType=USER
Please collect and share the OME logs for deeper troubleshooting. Based on the findings, Dell may recommend either rolling back to a previous OME version or waiting for a future OME release if the issue is confirmed to be software-related.
Additionally, could you please share the Service Tag of the system where OME is being used? Kindly provide it via Direct Message using the link above.
Dell-Ravi C
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!