Topic: Fail to Ban entries in iptables?
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: Ubuntu 18.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? N
====
Where does this line in my iptables come from? I cannot find where it's set in any config file
-A INPUT -p tcp -m multiport --dports 80,443,180,1443,25,587,465,110,995,143,993,4190 -j f2b-postfixIt's actually duplicated as is the f2b-postfix chain at the bottom of the table, i.e. two of each line.
-A f2b-postfix -j RETURNDeleting one line of each removes both lines from the iptables on reboot...
original table:
Generated by iptables-save v1.6.1 on Tue Sep 22 21:01:46 2020
*filter
:INPUT DROP [16439:2192857]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [704264:336205364]
:f2b-postfix - [0:0]
-A INPUT -p tcp -m multiport --dports 80,443,180,1443,25,587,465,110,995,143,993,4190 -j f2b-postfix
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 180 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 1443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 25 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 587 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 110 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 995 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 143 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 993 -j ACCEPT
-A f2b-postfix -j RETURN
-A f2b-postfix -j RETURN
COMMIT----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.