Hello Richard, Am Wed, May 21, 2025 at 05:48:43PM +0100 schrieb Richard Lewis: > On Tue, 20 May 2025, 17:29 Helge Kreutzmann, <[email protected]> wrote: > > Am Tue, May 20, 2025 at 12:41:15AM +0100 schrieb Richard Lewis: > > > On Mon, 19 May 2025 at 20:04, Mathias Gibbens <[email protected]> wrote: > > > > > > > > control: tags -1 + moreinfo unreproducible > > > > > > > > Having reviewed the messages so far in this bug report, it's clear > > > > that something different is happening when logcheck runs under the > > > > systemd timer/service, but not cron. However, we don't have a > > > > reproducer yet. > > > > > > i still cannot reproduce the original issue. > > > > If you need anything else, if I should turn something verbose etc., > > please let me know. > > > > im not sure quite what else to suggest. what we need is to know what exim > was trying to write. Mybe there is an exim option for that?
If there is, please tell me. I have no idea how exim works internally, sorry. > > All i see is the issue in > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106030 so > > > hopefully the workaround for that fixes this > > > > Should I locally implement this, i.e. return to stock logcheck 1.4.4? Ok, so I went back to the stock version, i.e. disregarded the debugging changes I made on your behalf. I also reinstalled procmail. > cant hurt - you can also do this locally: > > systemctl edit logcheck > # in the editor add: > [Service] > ExecStart=sleep 180 > > # im suggestibg a very long sleep, to give more chance to let exim do > something - or to write its paniclog I will do this once I get the double mails and report how it changes. Greetings Helge -- Dr. Helge Kreutzmann [email protected] 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
