CC @bjorn1
@bjorn1 any update on this? The issue seems to be the change in ClamAV's output format, which might need some tweaking on logwatch's side to handle the new ClamAV v1.0+ logs. Especially: "ClamAV update process started at Mon Jul 15 06:28:54 2024" vs "Mon Jul 15 06:28:54 2024 -> ClamAV update process started at Mon Jul 15 06:28:54 2024" (i.e. date prefix) I've created a bug report about this here: https://sourceforge.net/p/logwatch/bugs/125/
Cannot handle ClamAV 1.0+ logs