Discourse relies heavily on outgoing mail, setting SMTP up shouldn't be optional. my suggestion is to uncomment the lines responsible for smtp config in .env.sample
Discourse relies heavily on outgoing mail, setting SMTP up shouldn't be optional. my suggestion is to uncomment the lines responsible for smtp config in `.env.sample`
yeah that seems wise, Discourse can be used without email sending, but that's probably an unusual case which should require some kind of DISABLE_EMAIL setting to confirm
yeah that seems wise, Discourse _can_ be used without email sending, but that's probably an unusual case which should require some kind of `DISABLE_EMAIL` setting to confirm
Here is an example mail config for a 3rd party riseup notification setup:
# Outgoing email
DISCOURSE_SMTP_HOST=mail.riseup.net
DISCOURSE_SMTP_PORT=587
DISCOURSE_SMTP_USER=...
DISCOURSE_SMTP_PROTOCOL=tls
DISCOURSE_SMTP_AUTH=plain
# Set this if you send e-mails from a different domain than noreply@$DOMAIN
DISCOURSE_NOTIFICATION_EMAIL=$SMTP_USER
# SMTP authentication
COMPOSE_FILE="compose.yml:compose.smtpauth.yml"
SECRET_SMTP_PASSWORD_VERSION=v1
I think I still had to edit DISCOURSE_NOTIFICATION_EMAIL in the settings? Unsure.
Yeah, agree. Some random docs from my adventure:
I used the default admin user for myself and had to do https://docs.bitnami.com/aws/apps/discourse/configuration/change-default-email/ to change my email. Enabling SMTP and asking it to send a verficiation mail for a new email address didn't work.
Here is an example mail config for a 3rd party riseup notification setup:
```
# Outgoing email
DISCOURSE_SMTP_HOST=mail.riseup.net
DISCOURSE_SMTP_PORT=587
DISCOURSE_SMTP_USER=...
DISCOURSE_SMTP_PROTOCOL=tls
DISCOURSE_SMTP_AUTH=plain
# Set this if you send e-mails from a different domain than noreply@$DOMAIN
DISCOURSE_NOTIFICATION_EMAIL=$SMTP_USER
# SMTP authentication
COMPOSE_FILE="compose.yml:compose.smtpauth.yml"
SECRET_SMTP_PASSWORD_VERSION=v1
```
I think I still had to edit `DISCOURSE_NOTIFICATION_EMAIL` in the settings? Unsure.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Discourse relies heavily on outgoing mail, setting SMTP up shouldn't be optional. my suggestion is to uncomment the lines responsible for smtp config in
.env.sampleyeah that seems wise, Discourse can be used without email sending, but that's probably an unusual case which should require some kind of
DISABLE_EMAILsetting to confirmYeah, agree. Some random docs from my adventure:
I used the default admin user for myself and had to do https://docs.bitnami.com/aws/apps/discourse/configuration/change-default-email/ to change my email. Enabling SMTP and asking it to send a verficiation mail for a new email address didn't work.
Here is an example mail config for a 3rd party riseup notification setup:
I think I still had to edit
DISCOURSE_NOTIFICATION_EMAILin the settings? Unsure.