On Fri, 16 May 2025, 17:29 Helge Kreutzmann, <[email protected]> wrote:
> Hello Richard, > first of all, to test other configuration, I downgraded logcheck to > the previous version - now everything is back to normal. So this is not > an exim issue or so, but is clearly caused by the updated package. > (Logcheck > is running on this machines for many years). > thanks - all the other lines looked ok, although am confused by the exim output --- my guess is that this is an issue with systemd units exim. i didnt think this would affect the non-hardened unit, but: can you edit the logcheck script, and add a "sleep 30s" to the "end' , after the point the email is sent -- make sure to pick a point that will actually be run, i cant look right now, but search for where mime-construct is used. i think this may work -- i think that what is happening is: logcheck itself is ok, it makes the report and hands it to exim corrextly. but the systemd unit is shut down "too soon", while exim has taken in the mail - exim thinks something failed, tries to write to paniclog but cannot (i dont know why, but i suppose system closes all file descriptors.or.something). somehow exim retries later and you get a duplicate delivery --.actually you could check: is the mail id the same?. and if you run mailq between running logcheck and getting the 2nd mail, do you see a frozen/deferred message
