⚠️ This issue respects the following points: ⚠️
Bug description
On the admin Basic settings page (Administration settings → Basic settings → Email server),
the email/SMTP section has a "Send test e-mail" test button. When configuring SMTP for the first
time, clicking the test button before the settings are persisted makes the test run against the
old/empty configuration, so it fails — even though the entered values are correct. There is no hint
that the test uses saved values rather than the current form input. After the settings are saved, the same test succeeds.
This is confusing: it looks like the SMTP credentials are wrong when in fact only the
"save before test" ordering is the problem.
Steps to reproduce
- Go to Administration settings → Basic settings → Email server.
- Enter a fresh SMTP configuration (send mode, host, port, encryption, auth, username, app password).
- Immediately click Send test e-mail.
- The test fails / shows an error, despite correct values.
- Trigger a save, click Send test e-mail again → it now works.
Expected behavior
Either the test should be performed against the current form values, or the test button should be
disabled with a clear "save settings first" hint until the configuration has been persisted. At least the test button should be placed right of the save button.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
Apache (supported)
Database engine version
None
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Bug description
On the admin Basic settings page (Administration settings → Basic settings → Email server),
the email/SMTP section has a "Send test e-mail" test button. When configuring SMTP for the first
time, clicking the test button before the settings are persisted makes the test run against the
old/empty configuration, so it fails — even though the entered values are correct. There is no hint
that the test uses saved values rather than the current form input. After the settings are saved, the same test succeeds.
This is confusing: it looks like the SMTP credentials are wrong when in fact only the
"save before test" ordering is the problem.
Steps to reproduce
Expected behavior
Either the test should be performed against the current form values, or the test button should be
disabled with a clear "save settings first" hint until the configuration has been persisted. At least the test button should be placed right of the save button.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
Apache (supported)
Database engine version
None
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response