[Bug]: SMTP Authentication missing PLAIN option #37644
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
26-feedback
bug
feature: emails
needs info
stale
Ticket or PR with no recent activity
Comments
FReichelt
added
0. Needs triage
|
Logs: |
|
Cc @miaulalala |
|
Hi, you can ignore the option as it's dead code. Unfortunately I was unable to fix the frontend in time for the release. The EsmtpTransport class will go through 4 authenticators in this order: (Note for self: We don't filter the authenticators from config, although it could be done as a performance improvement, something to think about). Reference code: https://github.com/symfony/symfony/blob/6.3/src/Symfony/Component/Mailer/Transport/Smtp/EsmtpTransport.php |
|
I'm running v25 & v27 on two separate but identical machines. The email works fine on v25 as I have sent plain authentication the the internal mail server. The v27 machine only has Login but as you said it tries all 4 options but I get an |
|
The only way I could get it working was by switching to |
|
@chriscroome Thank you Chris. That worked a treat. Thankfully I only have a few installs. I hope they fix it in the next update. |
|
Good to hear @austserve however I'm not sure that unencrypted SMTP to port 25 on the
|
|
Ouch! Just when Protonmail opened up SMTP sending via token password for some none-business users, I stumble over this. Unfortunately Proton requires PLAIN authentication mode. Maybe this page needs an update then https://docs.nextcloud.com/server/19/admin_manual/configuration_server/email_configuration.html |
|
@DominusExult That page you referenced isn't the current documentation page - it's 8+ versions out of date. :) See |
|
To troubleshoot email sending problems please set both of the following in your Make sure there aren't an duplicate entries in your config. Then monitor the logs after triggering a test email. |
|
The way I understand it is that Symfony doesn't use PLAIN anymore, so the up to date docs might still need an update 🤷♂️ |
|
The docs could probably use improvement. However, PLAIN is definitely a supported authentication mode: The only party on this thread that has provided their configuration is the original reporter. There could be something going on for the other people. Giving there have been three different mailers I'm aware of across the span of NC's existence, there's bound to be some unnecessary overlap in some legacy configurations. The LOGIN being greyed out (in the original report of this issue from @FReichelt) was a cosmetic issue in the frontend. The option being there is no longer necessary. Hence the response from one of the developers in #37644 (comment). I suggest others having problems to turn on debug logging, review their That said, while bug reports are appreciated... If someone wants help debugging their particular configuration, the best place is to post for help is at the Nextcloud Help Forum. You can still post a bug report here if you feel it appropriate of course. |
|
@FReichelt This is your issue. Your original report was about not being able to set PLAIN. The answer is basically: you don't have to select anything for authentication anymore. All modes are attempted. I believe that was addressed here: And further it's been addressed by revising the UI since you reported the matter. Also the docs have been updated: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/email_configuration.html So was your issue addressed? Are you able to send email? I'll leave this issue open temporarily to see if you have feedback. Eventually it will close if there's no further feedback from you. Thank you for your report. |
|
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
I encountered a bug in Nextcloud where I am unable to set the SMTP authentication method to PLAIN. The only available option is to set it to LOGIN.
Steps to reproduce
Expected behavior
The Authentication Method dropdown should have two options: PLAIN and LOGIN. It should be possible to select either option depending on the user's preference.
Installation method
None
Nextcloud Server version
24
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
{ "system": { "memcache.local": "\\OC\\Memcache\\APCu", "apps_paths": [ { "path": "\/var\/www\/html\/apps", "url": "\/apps", "writable": false }, { "path": "\/var\/www\/html\/custom_apps", "url": "\/custom_apps", "writable": true } ], "memcache.distributed": "\\OC\\Memcache\\Redis", "memcache.locking": "\\OC\\Memcache\\Redis", "redis": { "host": "***REMOVED SENSITIVE VALUE***", "password": "***REMOVED SENSITIVE VALUE***", "port": 6379 }, "instanceid": "***REMOVED SENSITIVE VALUE***", "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "trusted_domains": [ "***REMOVED SENSITIVE VALUE***" ], "datadirectory": "***REMOVED SENSITIVE VALUE***", "dbtype": "pgsql", "version": "26.0.0.11", "overwriteprotocol": "https", "overwrite.cli.url": "***REMOVED SENSITIVE VALUE***", "trusted_proxies": "***REMOVED SENSITIVE VALUE***", "dbname": "***REMOVED SENSITIVE VALUE***", "dbhost": "***REMOVED SENSITIVE VALUE***", "dbport": "", "dbtableprefix": "oc_", "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "installed": true, "loglevel": 2, "maintenance": false, "mail_from_address": "***REMOVED SENSITIVE VALUE***", "mail_smtpmode": "smtp", "mail_sendmailmode": "smtp", "mail_domain": "***REMOVED SENSITIVE VALUE***", "mail_smtphost": "***REMOVED SENSITIVE VALUE***", "mail_smtpport": "465", "mail_smtpauth": 1 } }List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: