Skip to content

Commit 7c235e6

Browse files
authored
Add noreply setting to default docker compose file
I had to set this today because out of the box Zulip sends invites as noreply-<guid>@smtp.example.com instead of just [email protected], 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.
1 parent feec4de commit 7c235e6

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docker-compose.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,9 @@ services:
7979
SETTING_ZULIP_ADMINISTRATOR: "[email protected]"
8080
SETTING_EMAIL_HOST: "" # e.g. smtp.example.com
8181
SETTING_EMAIL_HOST_USER: "[email protected]"
82+
# Force [email protected] to send emails
83+
# See reasons to set it to True [here](https://zulip.readthedocs.io/en/latest/production/email.html#troubleshooting)
84+
SETTING_ADD_TOKENS_TO_NOREPLY_ADDRESS: 'False'
8285
SETTING_EMAIL_PORT: "587"
8386
# It seems that the email server needs to use ssl or tls and can't be used without it
8487
SETTING_EMAIL_USE_SSL: "False"

0 commit comments

Comments
 (0)