In this scenario, let's take a look at what happens when we are receiving an incoming mail.
May 24 22:07:19 mail postfix/smtpd: NOQUEUE: filter: RCPT from : : Sender address triggers FILTER smtp-amavis::10026 from= to= proto=ESMTP helo= May 24 22:07:19 mail postfix/smtpd: connect from Nonetheless, we will look at the logs for better understanding on the background process. Note that this will not work if the domain is not globally resolvable. In the next scenario, we will try sending a mail to Google. Mail postfix/smtpd: NOQUEUE: filter: RCPT from : : Sender address triggers FILTER smtp-amavis::10026 from= to= proto=ESMTP helo= The following is a snippet of the mail log in this scenario. After sending the mail, we can check the server log to see what went on under the hood. In this test, we first log in as user alpha, and try sending a test mail to user beta.
Iptables -A INPUT -p tcp -dport 7071 -j ACCEPT Iptables -A INPUT -p tcp -dport 9071 -j ACCEPT Iptables -A INPUT -p tcp -dport 3443 -j ACCEPT Iptables -A INPUT -p tcp -dport 995 -j ACCEPT Iptables -A INPUT -p tcp -dport 993 -j ACCEPT Iptables -A INPUT -p tcp -dport 587 -j ACCEPT Iptables -A INPUT -p tcp -dport 465 -j ACCEPT Iptables -A INPUT -p tcp -dport 443 -j ACCEPT Iptables -A INPUT -p tcp -dport 143 -j ACCEPT Iptables -A INPUT -p tcp -dport 110 -j ACCEPT Iptables -A INPUT -p tcp -dport 80 -j ACCEPT Iptables -A INPUT -p tcp -dport 25 -j ACCEPT Iptables -A INPUT -p tcp -dport 22 -j ACCEPT Iptables -A INPUT -m state -state ESTABLISHED,RELATED -j ACCEPT Iptables -A INPUT -s IP-Address-of-your-server/32 -j ACCEPT Always double check that your firewall rules are in compliance with your organization policies.
#ZIMBRA CHANGE EMAIL SERVER SETTINGS FREE#
I have used the following set of iptables rules as AWS CentOS 7 image comes pre-built with iptables, but feel free to use firewalld (the default firewall configuration tool for stock CentOS 7) to open all necessary Zimbra ports. Zimbra needs a number of ports opened in the firewall.
0 kommentar(er)
