The discussion revolves around configuring Discourse on Google Cloud to use G Suite SMTP for email sending. travisdeeth reports that while test emails work with the provided settings, registration emails fail to send. Despite trying various ports and configurations, including smtp-relay.gmail.com, the issue persists. mpalmer notes that Bitnami’s modifications make their Discourse setup unsupported, making troubleshooting difficult. travisdeeth points out discrepancies between Bitnami’s documentation and the official Discourse guide, highlighting the lack of an app.yml file. travisdeeth eventually resolves the issue by switching to a standard Ubuntu server, criticizing Bitnami for using an unsupported method and potentially profiting from it. codinghorror notes that Bitnami predates Docker, while mpalmer acknowledges the mystery behind Bitnami’s choices.
I am attempting to configure Discourse which is running through google cloud to use SMTP through G Suite. I am editing the “discourse.conf” found in “/opt/bitnami/apps/discourse/htdocs/config” to contain the following information;
When I use the above information the test email successfully goes through! But when I go to register, Discourse says it’s sending a confirmation email, but it never does.
I have also tried ports 465 and 2525 w/ the above information. I have also tried smtp_address = “smtp-relay.gmail.com”
The sections that contain asterisks are obviously to protect my private information.
We don’t know what weirdnesses Bitnami have done to their Discourse setup, so we can’t really provide much useful information. Have you tried the steps outlined in our official e-mail troubleshooting guide?
Well, I just switched from the generic Bitnami Discourse to an Ubuntu 16.04 server and ran the installer. It’s already working. Why is Bitnami packaging an opensource software and using a method that isn’t supported? I could be wrong, but they are probably profiting from it. The least they could do is do it the correct way.