MIAB as SMTP server for Discourse

[pl3bscheese]

I must be improperly configuring something. Mail is not sending from Discourse after setting up an instance.

Setup is:

MIAB hosted on server1
Discourse hosted on server2

app.yml shows:

  ## TODO: The mailserver this Discourse instance will use
  DISCOURSE_SMTP_ADDRESS: box.server1.us         # (mandatory)
  DISCOURSE_SMTP_PORT: 587                        # (optional)
  DISCOURSE_SMTP_USER_NAME: discourse@server1.us      # (optional)
  DISCOURSE_SMTP_PASSWORD: woowooithides               # (optional, WARNING the char '#' in pw can cause problems!)
  DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)

Do I need to setup additional records on MIAB for discourse to authenticate with BOX?

Suggestions would be much appreciated.

I entered app setup admin acct

./launcher enter app
rake admin:create

On the admin panel in discourse it shows this for email:

I think maybe the issue is plain authentication?

adding this line to app.yml:

  DISCOURSE_SMTP_AUTHENTICATION: "SSL"

rebuild in progress

Still a Fail

rebuilding with this addition:

DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: "none"

options are:

(none, peer, client_once, fail_if_no_peer_cert)

looks like I will try out each one hoping on success

partial success with:

DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)
DISCOURSE_SMTP_AUTHENTICATION: "plain"
DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none

[pl3bscheese]

[RESOLVED]

This thread:

Admin accounts should be permitted to send mail on behalf of other users

One of the problems I’ve encountered is that my web application needs to be able to send email on behalf of other users. Of course we don’t want to allow any arbitrary user to spoof another user’s account, but I believe that admin accounts, at least, should have this privilege. I was able to make this happen by modifying the query in /etc/postfix/sender-login-maps.cf: SELECT permitted_senders FROM ( SELECT permitted_senders FROM ( SELECT permitted_senders, …

Lead me to understand error was due to security setting aimed at blocking spoofed email

So recap when setting up Discourse with MIAB make the app.yml

## TODO: The mailserver this Discourse instance will use
DISCOURSE_SMTP_ADDRESS: box.server1.us         # (mandatory)
DISCOURSE_SMTP_PORT: 587                        # (optional)
DISCOURSE_SMTP_USER_NAME: discourse@server1.us      # (optional)
DISCOURSE_SMTP_PASSWORD: woowooithides               # (optional, WARNING the char '#' in pw can cause problems!)
DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)
DISCOURSE_SMTP_AUTHENTICATION: "plain"
DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none

& change the notification email option in the admin panel required settings to match the MIAB account sending out the mail

[meglio]

Shell we update the Discourse to use port 465? That’s what my MIAB admin console tells me to use for SMTP connections.