Hello Marc, Am Sat, May 17, 2025 at 05:44:03PM +0200 schrieb Marc Haber: > On Sat, May 17, 2025 at 01:44:57PM +0000, Helge Kreutzmann wrote: > > In /etc/exim4 three files mention procmail: > > > > exim4-config: /etc/exim4/conf.d/transport/30_exim4-config_procmail_pipe > > exim4-config: /etc/exim4/conf.d/router/700_exim4-config_procmail > > exim4-config: /etc/exim4/exim4.conf.template > > > > But I never edited them directly, only via Debconf (probably when I > > installed the machine. > > If you don't use procmail, you should deinstall it. Exim can deliver by > itself.
I use procmail on several machines, but right, on this one it is not (much) used. I just wonder - is procmail incompatible with the updated logcheck? > I have had much fun with sending e-mail from a systemd unit as well, but > that systemd unit is rather verbose and limited. I ended up using a helper > program to deliver mail and not calling /usr/lib/sendmail any more. See: > > https://salsa.debian.org/debian/aide/-/blob/debian/latest/debian/aide-common.dailyaidecheck.service > https://salsa.debian.org/debian/aide/-/blob/debian/latest/debian/aide-common.dailyaidecheck.timer > https://salsa.debian.org/debian/aide/-/blob/debian/latest/debian/bin/dailyaidecheck > > That was a pretty stiff amount of work. > > My first guess is that the suid bit does not work when /usr/lib/sendmail is > invoked from the systemd unit, and running as logcheck exim can indeed not > do anything. > My second guess is that for some reason Helge's system indeed runs > logcheck's classical cron job AND the new systemd timer, and the systemd > timer version shows the issue in question. I'd go ahead and debug why > logcheck's classical cron job doesn't get disabled on Helge's system. The difference, btw. which I see before and after the update, is the following: Before the update I get mails with the subject: Reboot: twentytwo.helgefjell.de 2025-05-16 15:54 +0200 System Events After the reboot, now mails with this subject are sent; however, the content is there (i.e. the filtered logs from the reboot are sent). The cron.log says (before the update): 2025-04-14T00:02:01.739639+02:00 twentytwo CRON[11492]: (logcheck) CMD ( if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi) and after the update: 2025-05-17T18:02:01.470178+02:00 twentytwo CRON[110761]: (logcheck) CMD ( if [ ! -d /run/systemd/system ] && [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi) So the cron commands changed during the update. file /run/systemd/system: /run/systemd/system: directory Should I revert this and look how it behaves? Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
