Bug#960009: postfix needs a new journalmatch parameter

2021-10-10 Thread Sylvestre Ledru
Le 10/10/2021 à 18:45, Mike Gerber a écrit : > 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. > >

Bug#960009: postfix needs a new journalmatch parameter

2021-10-10 Thread Mike Gerber
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

Bug#960009: postfix needs a new journalmatch parameter

2020-05-08 Thread martin f krafft
Regarding the following, written by "Sylvestre Ledru" on 2020-05-08 at 11:41 Uhr +0200: However, for version in stable, not sure what to do... I think this might qualify for a stable-update… -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'`

Bug#960009: postfix needs a new journalmatch parameter

2020-05-08 Thread Sylvestre Ledru
Hello Martin, Le 08/05/2020 à 11:23, martin f krafft a écrit : Untitled 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

Bug#960009: postfix needs a new journalmatch parameter

2020-05-08 Thread martin f krafft
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