Topic: postfix-iredmail
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
1.70
MySQL
Nginx
iRedAdmin-Pro - Yes
We have a client triggering the FAIL2BAN postfix-iredmail and getting banned.
I have looked in the /var/log/mail.log, and I can't find out why the
trigger is happening.
Thanks,
ABN
/var/log/mail.log
warning: hostname 173-165-103-33-Illinois.hfc.comcastbusiness.net does not resolve to address 173.165.103.33
root@nm2:~# cat /var/log/syslog | grep 173.165.103.33 | grep -i fail2ban
Nov 21 09:06:08 nm2 fail2ban.filter[664]: INFO [postfix-iredmail] Found 173.165.103.33 - 2024-11-21 09:06:08
Nov 21 09:06:26 nm2 fail2ban.filter[664]: INFO [postfix-iredmail] Found 173.165.103.33 - 2024-11-21 09:06:26
Nov 21 09:06:48 nm2 fail2ban.filter[664]: INFO [postfix-iredmail] Found 173.165.103.33 - 2024-11-21 09:06:48
Nov 21 09:07:04 nm2 fail2ban.filter[664]: INFO [postfix-iredmail] Found 173.165.103.33 - 2024-11-21 09:07:04
Nov 21 09:07:22 nm2 fail2ban.filter[664]: INFO [postfix-iredmail] Found 173.165.103.33 - 2024-11-21 09:07:22
Nov 21 09:07:22 nm2 fail2ban.actions[664]: NOTICE [postfix-iredmail] Ban 173.165.103.33
Is not find hostname enough to trigger ban?
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.