Topic: Whitelist Rules not working after reboot
==== Required information ====
- iRedMail version (check /etc/iredmail-release): v0.9.5-1
- Linux/BSD distribution name and version: CentOS 7 release 7.2.1511
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? v2.4.1 (MySQL)
- Related log if you're reporting an issue:
====
Hello,
We are notice that the IPtables rules and Whitelist rules are not keep in configuration after a reboot, one of our customers Public IP is getting banned immediately after the server starts. We must delete the block rule from the IPtables chain (f2b-postfix) and added it manually in order to get access from customer IP, even that the public IP was added in the fail2ban jail.conf as a trusted IP.
Also we modified the file iptables-config in /etc/sysconfig and change the following parameters:
================================================================
# Save current firewall rules on stop.
# Value: yes|no, default: no
# Saves all firewall rules to /etc/sysconfig/iptables if firewall gets stopped
# (e.g. on system shutdown).
IPTABLES_SAVE_ON_STOP="yes"
# Save current firewall rules on restart.
# Value: yes|no, default: no
# Saves all firewall rules to /etc/sysconfig/iptables if firewall gets
# restarted.
IPTABLES_SAVE_ON_RESTART="yes"
=================================================
Thanks in advance for the help you can provide us.
Regards,
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.