Separate the website from email delivery
A working Joomla homepage does not prove that registrations, contact forms or password resets can send email. A cloud instance is not automatically a managed mail service. Arrange an appropriate SMTP service and check its limits, authentication method and charges.
Also distinguish outbound delivery from mailboxes. Sending a password reset through an SMTP relay does not create an inbox for your business address.
Get the correct settings first
From your mail provider, obtain the SMTP hostname, port, encryption mode, authentication method and permitted sender address. Use provider-issued credentials with suitable limits rather than an everyday personal password where possible.
Follow that provider’s instructions for domain verification and DNS authentication. SPF and DKIM records must match the sending service; a DMARC policy also needs to account for every legitimate sender. Do not replace unrelated DNS records or add a second independent SPF record without checking the complete configuration.
Configure Joomla’s mail settings
In the Joomla administrator, open Global Configuration → Server → Mail Settings. Labels may vary by version.
| Setting | What to enter |
|---|---|
| From Email | A sender address authorised by your mail service |
| From Name | Your site or organisation’s recognisable name |
| Mailer | SMTP |
| SMTP Host | The provider’s exact hostname |
| SMTP Port / Security | The matching combination specified by the provider |
| SMTP Authentication | Enable when required by the provider |
| Username / credential | The account or SMTP credential supplied for this application |
Port 587 with STARTTLS and port 465 with implicit TLS are common arrangements; use the exact combination your provider supports. Do not solve a connection error by casually removing transport encryption. Newer Joomla versions may offer additional authentication options; confirm the mail provider and Joomla release both support the chosen method.
Save and use Joomla’s Send Test Mail action. If it fails, investigate the connection and authentication rather than assuming the recipient has a problem.
Test the real journeys
A successful core test does not prove every extension uses the same mail path. Test a contact form, a new registration and a password-reset request with accounts you control. Confirm the sender, reply-to address and destination.
For contact forms, keep an authorised domain address as the sender and put the visitor’s address in Reply-To where the extension supports it. Pretending to send directly from the visitor’s domain can fail authentication.
Check more than one receiving mailbox and inspect the sending provider’s delivery logs. “Accepted by SMTP” and “arrived in the inbox” are different observations.
Troubleshoot in order
Confirm the hostname and port, the encryption choice, whether server egress rules permit the connection, credentials, authorised sender and provider quota. Then inspect suppression lists, bounce messages, DNS authentication and receiving spam filters.
Do not publish logs containing passwords, tokens or customer addresses. Before cloning the site to staging, replace production email delivery with a safe test arrangement.
Source: Joomla Global Configuration documentation. Use your mail service’s current SMTP and DNS instructions for the exact values.