<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/logwatch/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/logwatch/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 30 Oct 2026 23:14:37 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/logwatch/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>systemd 257.13: New skipped format</title><link>https://sourceforge.net/p/logwatch/bugs/131/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello! I am still a big fan of your project, thank you!&lt;/p&gt;
&lt;p&gt;On one of my installations, Debian 13, upgrading systemd from 257.9 to 257.13, changed some log message formats:&lt;br/&gt;
Before: &lt;code&gt;systemd[1]: mdcheck_continue.service - MD array scrubbing - continuation was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/mdcheck/MD_UUID_*).&lt;/code&gt;&lt;br/&gt;
After: &lt;code&gt;systemd[1]: mdcheck_continue.service - MD array scrubbing - continuation skipped, unmet condition check ConditionPathExistsGlob=/var/lib/mdcheck/MD_UUID_*&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;I think the following pattern should be added:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="gh"&gt;diff --git a/scripts/services/systemd b/scripts/services/systemd&lt;/span&gt;
&lt;span class="gh"&gt;index 820e74d..056fae4 100644&lt;/span&gt;
&lt;span class="gd"&gt;--- a/scripts/services/systemd&lt;/span&gt;
&lt;span class="gi"&gt;+++ b/scripts/services/systemd&lt;/span&gt;
&lt;span class="gu"&gt;@@ -220,6 +220,8 @@ while (defined(my $ThisLine = &amp;lt;STDIN&amp;gt;)) {&lt;/span&gt;
&lt;span class="w"&gt; &lt;/span&gt;      $Skipped{$name}++ if $Detail;
&lt;span class="w"&gt; &lt;/span&gt;   } elsif (($name) = ($ThisLine =~ /^(.*) was skipped because/)) {
&lt;span class="w"&gt; &lt;/span&gt;      $Skipped{$name}++ if $Detail;

&lt;span class="gi"&gt;+   } elsif (($name) = ($ThisLine =~ /^(.*) skipped, unmet condition check/)) {&lt;/span&gt;
&lt;span class="gi"&gt;+      $Skipped{$name}++ if $Detail;&lt;/span&gt;
&lt;span class="w"&gt; &lt;/span&gt;   } elsif (($service) = ($ThisLine =~ /(\S+): Failed (?:to execute command|with result)/)) {
&lt;span class="w"&gt; &lt;/span&gt;      $Failed{$service}++;
&lt;span class="w"&gt; &lt;/span&gt;   } elsif (($service) = ($ThisLine =~ /(\S+) failed\.$/)) {
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;Best regards,&lt;br/&gt;
Jakob&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jakob Albert</dc:creator><pubDate>Fri, 30 Oct 2026 23:14:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7c7dfd8fca5e46792e8a58e84610919e090e54de</guid></item><item><title>#130 Issue with ignore.conf lines for exim </title><link>https://sourceforge.net/p/logwatch/bugs/130/?limit=25#4df9</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;That indeed fixes it. Thanks!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stamgastje</dc:creator><pubDate>Sun, 06 Sep 2026 08:15:28 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc6db856af9270fb631d31e7b8944e9286426c362</guid></item><item><title>#130 Issue with ignore.conf lines for exim </title><link>https://sourceforge.net/p/logwatch/bugs/130/?limit=25#9e26</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;New exim script pushed to repository; let us know if it fixes it.  As per the link you provided, openssl reports it depending on its version.  For this script, I've pushed it to only print if Detail is above 50, as is already the case for other log statements in this script.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bjorn </dc:creator><pubDate>Sun, 06 Sep 2026 02:38:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc4ce23a5fe565b5bca2009686c07438997bd7320</guid></item><item><title>Issue with ignore.conf lines for exim </title><link>https://sourceforge.net/p/logwatch/bugs/130/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have many lines in the log indicating that "The TLS connection was non-properly terminated."&lt;/p&gt;
&lt;p&gt;Examples from /var/log/exim4/mainlog:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="gh"&gt;#&lt;/span&gt; 2026-08-09 07:31:27 TLS error on connection from (7se3rjd91m09u7yuv0d2ss) [122.187.230.41] (recv): The TLS connection was non-properly terminated.
&lt;span class="gh"&gt;#&lt;/span&gt; 2026-08-09 07:47:56 TLS error on connection from [208.69.161.214] (gnutls_handshake): The TLS connection was non-properly terminated.
&lt;span class="gh"&gt;#&lt;/span&gt; 2026-08-09 09:29:06 TLS error on connection from maile-ac.linkedin.com [108.174.3.195] (recv): The TLS connection was non-properly terminated.
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;The logwatch output I get is as follows:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt; --- TLS Connection Issues 
   ...
    gnutls_handshake: The TLS connection was non-properly terminated: 1 Time(s)
   recv: The TLS connection was non-properly terminated: 4 Time(s)
   ...

  From these hosts:
   ...
   mailb-hf.linkedin.com: 1 Time(s)
   maile-ad.linkedin.com: 1 Time(s)
   maile-bb.linkedin.com: 1 Time(s)
   maile-df.linkedin.com: 1 Time(s)
   maile-ge.linkedin.com: 1 Time(s)
   maile-hc.linkedin.com: 1 Time(s)
   maile-hf.linkedin.com: 1 Time(s)
   ...
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;The reason why exim throws these warnings seems to be that some servers intentionally omit TLS close_notify on connection close to save a roundtrip, despite it being against the TLS protocol. See: &lt;a href="https://github.com/Exim/exim/pull/94." rel="nofollow"&gt;https://github.com/Exim/exim/pull/94.&lt;/a&gt; Hence, hey are basically false positives / noise.&lt;/p&gt;
&lt;p&gt;To suppress those warnings, I've added the following regular expression in my ignore.conf file:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;.+: The TLS connection was non-properly terminated.
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;This only partially works; I do no longer such  these lines lines in the output:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;   gnutls_handshake: The TLS connection was non-properly terminated: 1 Time(s)
   recv: The TLS connection was non-properly terminated: 4 Time(s)
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;However, I still see the following output:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt; --- TLS Connection Issues 
   ...

  From these hosts:
   ...
   mailb-hf.linkedin.com: 1 Time(s)
   maile-ad.linkedin.com: 1 Time(s)
   maile-bb.linkedin.com: 1 Time(s)
   maile-df.linkedin.com: 1 Time(s)
   maile-ge.linkedin.com: 1 Time(s)
   maile-hc.linkedin.com: 1 Time(s)
   maile-hf.linkedin.com: 1 Time(s)
   ...
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;And I've checked my exim logs and these hosts are only producing those warnings (and not also other warnings).  Hence, it seems that only suppresses the warning lines, but still lists the hosts in those lines. &lt;/p&gt;
&lt;p&gt;Am I doing something wrong? Or is this a bug in logwatch?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stamgastje</dc:creator><pubDate>Fri, 14 Aug 2026 07:31:54 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7ea9d1e7c1b690aede3d6445d194ee15bbdc5300</guid></item><item><title>#127 logwatch cron uses erroneous path in newer EL versions.</title><link>https://sourceforge.net/p/logwatch/bugs/127/?limit=25#9c0b</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bjorn </dc:creator><pubDate>Wed, 22 Jul 2026 19:02:00 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6ea11efc26163e061c661a3761aeae6ae47edbec</guid></item><item><title>#129 dovecot 2.4: handle changed log format for aborted logins </title><link>https://sourceforge.net/p/logwatch/bugs/129/?limit=25#59f5</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Folks, I've picked up items from both of these requests and pushed an update to dovecot for them.&lt;/p&gt;
&lt;p&gt;Please check if they address all the issues.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Frank Crawford</dc:creator><pubDate>Fri, 17 Jul 2026 02:19:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0bc4020c27a0da4c7b9acef8ab499d2b8fae2715</guid></item><item><title>#127 logwatch cron uses erroneous path in newer EL versions.</title><link>https://sourceforge.net/p/logwatch/bugs/127/?limit=25#6487</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Pushed change to /usr/bin rather than /usr/sbin as executable for logwatch (which is a symbolic link to the /usr/share/logwatch/scripts/logwatch.pl script).&lt;br/&gt;
Does not delete any links under /usr/sbin/logwatch.  For existing systems, the old link continues to work.  For new installations, only the new /usr/bin/logwatch link will work.&lt;br/&gt;
Also deleted the requirement for &lt;code&gt;crontabs&lt;/code&gt; package, as newer installations may use alternate scheduling tools (most notably systemd timers).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bjorn </dc:creator><pubDate>Thu, 02 Jul 2026 17:06:11 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net750e7755bd7bce300dece6b0f4fa3200f6c804ce</guid></item><item><title>#129 dovecot 2.4: handle changed log format for aborted logins </title><link>https://sourceforge.net/p/logwatch/bugs/129/?limit=25#5668</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: closed-accepted --&amp;gt; open&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bjorn </dc:creator><pubDate>Tue, 02 Jun 2026 04:17:00 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net11a60227a8b84a41e6dab1a1323fbafb8128047e</guid></item><item><title>#129 dovecot 2.4: handle changed log format for aborted logins </title><link>https://sourceforge.net/p/logwatch/bugs/129/?limit=25#ed2b</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Now I see that both change requests might have overlapped.  So maybe submit it as a patch file from the prior dovecot or, even better, as either a patch file or a merge request from the current repository's version.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bjorn </dc:creator><pubDate>Tue, 02 Jun 2026 04:09:07 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net031339a9cb40c2e9be3a692761b8d4ebccd3912d</guid></item><item><title>#129 dovecot 2.4: handle changed log format for aborted logins </title><link>https://sourceforge.net/p/logwatch/bugs/129/?limit=25#0830</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Can you re-submit the merge request with the new base?  Your previous patch was already saved to the repository.  So your working &lt;code&gt;dovecot&lt;/code&gt; file should be the correct version, with the additional changes.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bjorn </dc:creator><pubDate>Tue, 02 Jun 2026 04:03:57 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net40ed68f41d9853ef5e2c088f406f9115aa930d60</guid></item></channel></rss>