From 7c235e64f221ab29d08086a5321c1c965c3ad044 Mon Sep 17 00:00:00 2001 From: Eevoo <49214133+Eevoo@users.noreply.github.com> Date: Sun, 12 Sep 2021 07:52:13 -0400 Subject: [PATCH] Add noreply setting to default docker compose file I had to set this today because out of the box Zulip sends invites as noreply-@smtp.example.com instead of just noreply@smtp.example.com, which was causing email bounces as I didn't have a sending identity for that particular email address. The default is true for security reasons as listed in [this hack](https://medium.com/intigriti/how-i-hacked-hundreds-of-companies-through-their-helpdesk-b7680ddc2d4c), but I'd argue setting this setting to default to False will be the most pain-free way for most self-hosted users that are only running Zulip and not running it alongside an 'email to public support ticket tracker' feature. Having said that, even if it is preferred to leave this at True, it will still help smooth the way for self-hosted users to find and change this setting up front rather than needing to track this down and manually create the setting. --- docker-compose.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index 8ac6b5be96..f9e4f50519 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -79,6 +79,9 @@ services: SETTING_ZULIP_ADMINISTRATOR: "admin@example.com" SETTING_EMAIL_HOST: "" # e.g. smtp.example.com SETTING_EMAIL_HOST_USER: "noreply@example.com" + # Force noreply@example.com to send emails + # See reasons to set it to True [here](https://zulip.readthedocs.io/en/latest/production/email.html#troubleshooting) + SETTING_ADD_TOKENS_TO_NOREPLY_ADDRESS: 'False' SETTING_EMAIL_PORT: "587" # It seems that the email server needs to use ssl or tls and can't be used without it SETTING_EMAIL_USE_SSL: "False"