An update - closing this "bug" report My apologies for wasting your time but the failure of the logwatch custom setup for msmtp on July 2 had nothing to do with Debian or any upgrades.
The date format used by msmtp for their logs uses a leading 0 (zero) for days with single digits whereas the standard syslog date format uses a leading blank. As long as the day was double digit (I installed the custom setup on June 15 so all dates were good until June 309) logwatch properly found the relevant dates. But when, on July 2, logwatch tried to process the July 1 report, it could find no matching dates for "yesterday" and therefore did not report any activity for msmtp. Problem now fixed and Debian had nothing to do with it. R -----Original Message----- From: Debian Bug Tracking System [mailto:ow...@bugs.debian.org] Sent: July 5, 2020 9:51 AM To: priv...@ayuda.ca Subject: Bug#964259: Info received (Bug#964259: Acknowledgement (libseccomp2 upgraded from 2.4.1-0ubuntu0.18.04.2 => 2.4.3-1ubuntu3.18.04.2 , logwatch service stopped)) Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Kees Cook <k...@debian.org> If you wish to submit further information on this problem, please send it to 964...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 964259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
