@Stephen, you’re telling me that using an email SMTP service provider that is not within the recommended providers is considered outside of the supported track???
If so, that’s pretty incredible to suggest that using a standard Exim email server that works normally for email clients. Further, some of us like to have control over our mail servers vs trusting others with our mail content. I think that this is one of the attractions of Discourse - own your data - and as such, you’ll find that more and more folks will want to not use such free / bulk options as these.
At any rate, I’ll keep soldiering on here for these very reasons. cPanel SMTP servers should be quite supported.
So it’s quite interesting, I think the key here is that the following works both outside of the Docker container and within the Docker container (
/var/discourse/launcher enter app):
openssl s_client -connect xxx.xxx.xxx.xxx:465 -servername mail.domain.tld -showcerts -quiet
depth=2 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Certification Authority
depth=1 C = US, ST = TX, L = Houston, O = "cPanel, Inc.", CN = "cPanel, Inc. Certification Authority"
depth=0 CN = domain.tld
220-server.domain.tld ESMTP Exim 4.91 #1 Sun, 25 Nov 2018 21:22:35 -0500
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
With this I’m able to access the mail server without issue and issue commands.
However when I use these settings within
containers/app.yml and then run
./discourse-doctor I’m hitting a wall with:
This clearly seems to be something going on with Discourse itself and yet I’m not seeing anything meaningful in the logs about this, which I find peculiar.