Why port 587 is shown as closed if I have opened it in /etc/shorewall/rules?

by Santiago Madrid   Last Updated July 12, 2019 00:00 AM

I've installed recently Shorewall firewall and I've setted a rule that ACCEPT incoming TCP conections from network to my host. I've made this changes in /etc/shorewall/rules file but then, when I execute nmap, the port is shown closed as you can see in the output below:

Nmap scan report for mail.xxxxxxx.com (xxx.xxx.xxx.xxx)
Host is up (0.00090s latency).
rDNS record for xxx.xxx.xxx.xxx: ec2-xx-xx9-xx-xx.sa-east-1.compute.amazonaws.com
Not shown: 995 filtered ports
PORT    STATE  SERVICE
25/tcp  open   smtp
80/tcp  open   http
110/tcp open   pop3
143/tcp open   imap
587/tcp closed submission

I've deactivated ufw firwall. I'm running an Ubuntu server 16.04



Related Questions


Updated March 21, 2019 08:00 AM

Updated June 22, 2018 05:00 AM

Updated June 14, 2016 08:00 AM

Updated September 16, 2017 09:00 AM

Updated August 16, 2018 15:00 PM