#960009 postfix needs a new journalmatch parameter

Package:
fail2ban
Source:
fail2ban
Submitter:
martin f krafft
Date:
2021-10-10 18:03:02 UTC
Severity:
normal
#960009#3
Date:
2020-05-08 09:23:00 UTC
From:
To:
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
#960009#8
Date:
2020-05-08 09:41:08 UTC
From:
To:
Hello Martin,

Le 08/05/2020 à 11:23, martin f krafft a écrit :
I guess it is already fixed in testing.

However, for version in stable, not sure what to do...

Cheers,

S
#960009#13
Date:
2020-05-08 10:07:05 UTC
From:
To:
Regarding the following, written by "Sylvestre Ledru" on 2020-05-08 at 11:41 Uhr +0200:

I think this might qualify for a stable-update…
#960009#18
Date:
2021-10-10 16:45:51 UTC
From:
To:
found 960009 0.11.2-2

This bug is also affecting bullseye. The default postfix instance logs
to _SYSTEMD_UNIT=postfix@-.service, see also
/usr/share/doc/postfix/README.Debian.gz. Changing the journalmatch
accordingly fixes the problem.


Workaround in terms of ansible:


- name: "fix up postfix filter journalmatch (debian)"
   lineinfile:
     path: /etc/fail2ban/filter.d/postfix.conf
     regex: '^journalmatch'
     line: 'journalmatch = _SYSTEMD_UNIT=postfix@-.service'
   when: ansible_distribution == 'Debian' or ansible_distribution ==
'Ubuntu'
   notify: restart fail2ban


Should I submit a patch?
#960009#25
Date:
2021-10-10 17:59:00 UTC
From:
To:
Le 10/10/2021 à 18:45, Mike Gerber a écrit :
yeah go ahead and propose a MR here:

https://salsa.debian.org/python-team/packages/fail2ban

many thanks

S