?
avatar jjnxpct
jjnxpct
1 Dec 2020

Steps to reproduce the issue

We use SMTP settings (Global configuration - > Server ->Mail Settings) to e-mail CMS messages. This has been workin OK, but now (since last Joomla update??) when we send a test message we get a message like this:
The email was sent to ************ but using PHP Mail as fallback. You should check that you've received the test email.

Expected result

The email should be send using the SMTP settings and not fall back using PHP mail.

Actual result

PHP mail is used.

System information (as much as possible)

Joomla 3.9.26
PHP 7.4.11

Additional comments

has the PHP mail fallback always been there? I have not noticed it before. I only remember a warning when the SMTP settings were not correct when sending a test mail from the backend.

avatar jjnxpct jjnxpct - open - 1 Dec 2020
avatar joomla-cms-bot joomla-cms-bot - change - 1 Dec 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 1 Dec 2020
avatar jjnxpct
jjnxpct - comment - 1 Dec 2020

Ah, wait. I found a change in Joomla that causes this 'issue'. It seems because of a security fix you need to enter the password in the (greyed-out) password field before sending the test (don't save first). I guess having the password in the form is not secure and so the password is not actually used when sending the test. I have tired this an now SMTP is used OK.

So to test SMTP: Save the SMTP settings, then fill out the password in the password field, (don';t save) send a test mail. This gives a message that the mail has been send using SMTP. And not the fallback message.

It might be good to inform the backend user about this somehow. May with some info below the test button? But because this is Joomla 3 probably no more changes will be made...

avatar gostn
gostn - comment - 1 Dec 2020

duplicate #31482

avatar HLeithner HLeithner - change - 1 Dec 2020
Status New Closed
Closed_Date 0000-00-00 00:00:00 2020-12-01 10:34:02
Closed_By HLeithner
avatar HLeithner HLeithner - close - 1 Dec 2020

Add a Comment

Login with GitHub to post a comment