Package: fail2ban Version: 0.10.2-2.1 Severity: normal File: /etc/fail2ban/filter.d/postfix.conf
Postfix is started by systemd as postfix@-.service since 3.1.0-3.1 (June 2016), which means that the journalmatch parameter needs to be updated to the above. This also opens the question about what to do with multiple instances. Ideally, the journalmatch parameter could be parametrised and defined in the jail? Thanks, martin -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fail2ban depends on: ii lsb-base 11.1.0 ii python3 3.8.2-3 Versions of packages fail2ban recommends: ii iptables 1.8.4-3 ii nftables 0.9.4-1 pn python3-pyinotify <none> pn python3-systemd <none> ii whois 5.5.6 Versions of packages fail2ban suggests: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1+b1 pn monit <none> ii rsyslog [system-log-daemon] 8.2002.0-2 ii sqlite3 3.31.1-5 -- .''`. martin f. krafft <madduck@d.o> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
