How to Test Joomla Email Settings
Start with Joomla's built-in test
Go to System → Global Configuration → Server and locate the Mail section. Verify the visible settings, save if needed, and select Send Test Mail. Joomla sends the test to the email address associated with the current administrator account, so confirm that account has a valid destination address before interpreting the result.
Check both the Joomla response and the mailbox
A success message means the sending process did not report an immediate application error; it does not prove final delivery. Check the destination inbox, spam or junk folder, quarantine, and provider message trace. Allow for normal delivery delay before declaring the test lost.
Test the real feature that matters
After the global test works, trigger the actual Joomla or extension event you depend on: registration, password reset, contact form, workflow notification, or another message. An extension can have its own recipient, template, sender, or logic problem even when Joomla's global test succeeds.
Use Joomla mail debugging when necessary
For difficult SMTP failures, Joomla's documentation describes enabling System - Debug for an appropriate restricted group, enabling Debug System, using Maximum error reporting, enabling broad logging, and adding the mail log category. Then run the test and inspect the protected log output for the failure details.
Do not leave debug settings enabled
Verbose debugging and maximum error reporting can expose operational information and add noisy logs. After collecting the evidence, restore the site's intended production error-reporting and debugging settings. Keep downloaded diagnostic logs protected because they may contain addresses, server details, or other sensitive information.
Separate connection from delivery problems
Connection refused, timeout, certificate/TLS, and authentication errors occur before successful submission. A message accepted by the SMTP service but missing at the recipient points instead toward sender policy, filtering, reputation, DNS authentication, routing, or recipient-side controls. Troubleshoot the layer that actually failed.
Retest after infrastructure changes
Run a controlled email test after changing hosts, PHP versions, DNS, SMTP providers, credentials, firewall rules, or Joomla versions. Also test after major mail-template or extension changes. Periodic testing is especially useful for sites where important notifications are sent only occasionally.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.