From bc5abb2aed13e0f25218bffbad16f5b46baebf83 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Peters?= Date: Thu, 14 Dec 2017 21:56:34 +0100 Subject: [PATCH] Update firststeps-local_mta.md --- docs/firststeps-local_mta.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/firststeps-local_mta.md b/docs/firststeps-local_mta.md index 17bb713c8..b7f7835d8 100644 --- a/docs/firststeps-local_mta.md +++ b/docs/firststeps-local_mta.md @@ -11,8 +11,12 @@ Furthermore, to relay over a dockerized mailcow, you may want to add `172.22.1.1 postconf -e 'relayhost = 172.22.1.1' postconf -e "mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128" postconf -e "inet_interfaces = loopback-only" +postconf -e "relay_transport = relay" +postconf -e "default_transport = smtp" ``` +**Now it is important** to not have the same FQDN in `myhostname` as you use for your dockerized mailcow. Check your local (non-Docker) Postfix' main.cf for `myhostname` and set it to something different, for example `local.my.fqdn.tld`. + "172.22.1.1" is the mailcow created network gateway in Docker. Relaying over this interface is necessary (instead of - for example - relaying directly over ${MAILCOW_HOSTNAME}) to relay over a known internal network.