A user, Kristian, reports that their DigitalOcean Discourse droplet cannot send emails, receiving a “504 5.7.4 Unrecognized authentication type” error when using Office 365 SMTP settings. Despite correct configuration in app.yml (including DISCOURSE_SMTP_AUTHENTICATION: login and DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none), emails are not delivered. A test using s-nail inside the container successfully sent mail, suggesting the issue may be related to authentication or SSL verification. Other users, including Capstan, confirm similar issues with Office 365 SMTP, and a suggestion to check valid authentication types is made. Kristian eventually gives up and switches solutions, while m.jason.miller confirms that setting DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none resolved their problem.
FAILED
--------------------
Pups::ExecError: rails r "SiteSetting.notification_email='foo@bar.com'"` failed with return #<Process::Status: pid 2229 exit 2>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params "rails r \"SiteSetting.notification_email='foo@bar.com'\"`"
9628e31c775b74ad0f3a555b6af27701aa40b1f8b86419fa44a7c389cc5e34ae
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
I’m having this problem also. I spun up a droplet with Discourse on Digital Ocean as well. I used the “sudo ./discourse-doctor” command after trying all of these suggestions and rebuilding each time ( sudo ./launcher rebuild app).
504 5.7.4 Unrecognized authentication type [BL0PR01CA0015.prod.exchangelabs.com]
s-nail from within the container did work for me also, no problem. And I tried it without the “-S ssl-verify=ignore” clause, worked fine. Can someone verify that what gets installed on the digital ocean droplet does send email correctly?