docs: Clarify access to port 25 is needed for local email delivery.

This commit is contained in:
Alex Vandiver 2023-06-07 14:40:42 +00:00 committed by Tim Abbott
parent f420f433a4
commit bad600e731
1 changed files with 6 additions and 2 deletions

View File

@ -26,8 +26,8 @@ There are two ways to configure Zulip's email gateway:
The local delivery configuration is preferred for production because The local delivery configuration is preferred for production because
it supports nicer looking email addresses and has no cron delay. The it supports nicer looking email addresses and has no cron delay. The
polling option is convenient for testing/developing this feature polling option is convenient for testing/developing this feature
because it doesn't require a public IP address or setting up MX because it doesn't require a public IP address, setting up MX
records in DNS. records in DNS, or adjusting firewalls.
:::{note} :::{note}
Incoming emails are rate-limited, with the following limits: 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 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. Log in to your Zulip server; the remaining steps all happen there.
1. Add `, zulip::postfix_localmail` to `puppet_classes` in 1. Add `, zulip::postfix_localmail` to `puppet_classes` in