From bad600e731d405a5180d3b1991f421e8d95f0801 Mon Sep 17 00:00:00 2001 From: Alex Vandiver Date: Wed, 7 Jun 2023 14:40:42 +0000 Subject: [PATCH] docs: Clarify access to port 25 is needed for local email delivery. --- docs/production/email-gateway.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/production/email-gateway.md b/docs/production/email-gateway.md index 077033baed..218d0a24db 100644 --- a/docs/production/email-gateway.md +++ b/docs/production/email-gateway.md @@ -26,8 +26,8 @@ There are two ways to configure Zulip's email gateway: The local delivery configuration is preferred for production because it supports nicer looking email addresses and has no cron delay. The polling option is convenient for testing/developing this feature -because it doesn't require a public IP address or setting up MX -records in DNS. +because it doesn't require a public IP address, setting up MX +records in DNS, or adjusting firewalls. :::{note} Incoming emails are rate-limited, with the following limits: @@ -62,6 +62,10 @@ using an [HTTP reverse proxy][reverse-proxy]). 1 hostname.example.com ``` +1. If you have a network firewall enabled, configure it to allow incoming access + to port 25 on the Zulip server from the public internet. Other mail servers + will need to use it to deliver emails to Zulip. + 1. Log in to your Zulip server; the remaining steps all happen there. 1. Add `, zulip::postfix_localmail` to `puppet_classes` in