Authenticated SMTP gives a website or application an explicit sending identity and clearer error reporting than relying on an unspecified local mail path. Use a dedicated authorised mailbox and the connection details published for that account.
IN THIS ARTICLE
Check access and requirements
Check the application supports SMTP with TLS and protect its configuration secrets. Confirm the mailbox is allowed to send the intended message volume and type. Transactional mail and bulk campaigns may need different approved services.
01 Configure an application to send through authenticated SMTP
- Open Email Accounts > Connect Devices for the intended address and copy the displayed secure outgoing server settings.
- Enter the full mailbox address as the SMTP username and its mailbox password in the application’s protected settings. Do not use the cPanel owner password.
- Match the encryption mode and port exactly. Implicit TLS and STARTTLS are different modes; use the provider-supported pairing rather than mixing them.
- Set a From address the service permits and a monitored Reply-To address. Save without exposing credentials in a public configuration file or repository.
- Send a uniquely named test to an external mailbox. Review the application log and Track Delivery, then test the real notification workflow.
02 Example: match the SMTP port to its encryption mode
These are common submission modes, not a replacement for the settings shown for your mailbox in Connect Devices.
| Mode | Common port | What the application must do |
|---|---|---|
| Implicit TLS, often labelled SSL/TLS | 465 |
Start the TLS connection immediately, then authenticate inside that encrypted connection. |
| STARTTLS | 587 |
Upgrade the SMTP connection to TLS and require that upgrade to succeed before authenticating or submitting mail. |
For example, an application set to STARTTLS while connecting to a server port expecting immediate TLS can fail before the mailbox password is checked. Match the hostname, port and encryption mode together, and keep certificate verification enabled. Labels vary between applications, so check the application documentation when a setting is described only as TLS.
Confirm the expected result
The message should arrive with the intended sender, a usable reply address and expected authentication results. Application success normally means SMTP acceptance, so also inspect recipient spam folders when necessary.
Resolve setup problems
Authentication errors usually require checking the full username, password and mailbox restriction. Connection failures can involve DNS, port access or TLS mismatch. Never disable certificate verification as the routine fix for a hostname mismatch; use the correct service hostname.
How should I rotate the password?
Plan the change across every legitimate application using that mailbox, update each protected secret store and verify sending afterwards. A dedicated application mailbox makes this inventory easier.
.png)
 (1).jpg)
 (1) (1).png)
 (1).png)
.jpg)
.jpg)
 (1).jpg)
.jpg)
