<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/logwatch/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/logwatch/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/logwatch/discussion/</id><updated>2025-11-11T00:52:44.313000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>sshd journalctl doesn't seem to work</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/c48bab0403/?limit=25#3dc8" rel="alternate"/><published>2025-11-11T00:52:44.313000Z</published><updated>2025-11-11T00:52:44.313000Z</updated><author><name>Skibbi</name><uri>https://sourceforge.net/u/skibbi/</uri></author><id>https://sourceforge.net9f10ba5aa9f3e100358a56181d195ff525429e30</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'm back with more questions - recently I updated logwatch in my debian (forky) to 7.13. My &lt;code&gt;sshd.conf&lt;/code&gt; is following:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;Logfile =
Logfile = none
*JournalCtl = "_SYSTEMD_UNIT=ssh.service -o short-iso"
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;But it seems logwatch cannot parse the date from journalctl :(&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;**Unmatched Entries**
 2025-11-10T17:57:07+01:00 gw-02 sshd-session[68506]: Accepted publickey for debian from 192.168.5.45 port 46214 ssh2: ED25519 SHA256:&amp;lt;redacted&amp;gt; : 1 Time
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;The only solution that I found working is to set:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;*JournalCtl = "_SYSTEMD_UNIT=ssh.service -o cat --since yesterday --until today"
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;But that makes the &lt;code&gt;--range&lt;/code&gt; useless. Any tips how to format date in journalctl so it can be parsed correctly by logwatch?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=250#72a1" rel="alternate"/><published>2025-09-12T00:48:18.218000Z</published><updated>2025-09-12T00:48:18.218000Z</updated><author><name>Vladimir Lomov</name><uri>https://sourceforge.net/u/lomov_vl/</uri></author><id>https://sourceforge.net04ee822953412dd80425cd5236356b6f5eb569aa</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;For the future contributions will do as you suggested.&lt;/p&gt;
&lt;p&gt;P.S. I didn't check the link, but I thought it should give raw file. I checked now (by curl) and it output the patch.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=25#6b14" rel="alternate"/><published>2025-09-11T04:59:18.932000Z</published><updated>2025-09-11T04:59:18.932000Z</updated><author><name>Bjorn </name><uri>https://sourceforge.net/u/bjorn1/</uri></author><id>https://sourceforge.netd7f64c2de486ddb553b21db34a26a7eb6ad435f7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Patch applied to the repository.  For future reference, just attach the output of the diff as the patch file.  The attachment you provided is an html file, not a patch file.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=250#f8cd" rel="alternate"/><published>2025-09-11T00:07:43.771000Z</published><updated>2025-09-11T00:07:43.771000Z</updated><author><name>Vladimir Lomov</name><uri>https://sourceforge.net/u/lomov_vl/</uri></author><id>https://sourceforge.netbd3ec0ae8d7501595ae0ad53ad8b8fa9bd1dc40c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;a class="user-mention" href="/u/bjorn1/profile/"&gt;@bjorn1&lt;/a&gt;,&lt;br/&gt;
sorry, I didn't pay attention to the topic. Thank you for incorporating the patch, but there were two problems with the applied patch. Would you mind applying the fix (&lt;a class="" href="https://git.sr.ht/~vp1981/pkgbuild/blob/master/logwatch/0001-scripts-services-dovecot-fix-two-typos.patch" rel="nofollow"&gt;here&lt;/a&gt; and attached to the thread).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=25#ecb3" rel="alternate"/><published>2025-09-09T04:51:09.154000Z</published><updated>2025-09-09T04:51:09.154000Z</updated><author><name>Bjorn </name><uri>https://sourceforge.net/u/bjorn1/</uri></author><id>https://sourceforge.netfa832eaa777643c11a0ee69cbc849de8dfdb4f36</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I think I found a version of your patch, which it's been incorporated in the repository.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=25#6745" rel="alternate"/><published>2025-08-27T01:05:35.865000Z</published><updated>2025-08-27T01:05:35.865000Z</updated><author><name>Bjorn </name><uri>https://sourceforge.net/u/bjorn1/</uri></author><id>https://sourceforge.nete9233902beeb1819fa25ff3a3fe6c72e741c473d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The link is not valid.  Can you re-post the patch as an attachment?  That's for the 2.4 changes; the correction to the spacing was already committed.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=250#ba20" rel="alternate"/><published>2025-08-26T07:29:02.854000Z</published><updated>2025-08-26T07:29:02.854000Z</updated><author><name>Vladimir Lomov</name><uri>https://sourceforge.net/u/lomov_vl/</uri></author><id>https://sourceforge.net0cf853763859e38e5d5a5e3fe1f4ddc5b02f0328</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Sorry for the inconvenience of renaming the patch.&lt;/p&gt;
&lt;p&gt;Since the previous attempt gave me more or less the desired result, I tried to handle other "&lt;code&gt;Unmatched entries&lt;/code&gt;". The new patch is &lt;a href="https://git.sr.ht/~vp1981/pkgbuild/blob/master/logwatch/0002-dovecot-2.4-log-format-support.patch." rel="nofollow"&gt;https://git.sr.ht/~vp1981/pkgbuild/blob/master/logwatch/0002-dovecot-2.4-log-format-support.patch.&lt;/a&gt; It collects the &lt;code&gt;no_auth_attempts&lt;/code&gt; and &lt;code&gt;tls_handshake_not_finished&lt;/code&gt; entries, but it doesn't include the "reason". I'm still not sure how detailed the information should be.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dovecot 2.4+ log support</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/7bd6a84ea0/?limit=250#49cf" rel="alternate"/><published>2025-08-25T02:05:53.718000Z</published><updated>2025-08-25T02:05:53.718000Z</updated><author><name>Vladimir Lomov</name><uri>https://sourceforge.net/u/lomov_vl/</uri></author><id>https://sourceforge.net04b0838cdd7ef5d51d0baa1b6f15fe456278bccb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello.&lt;/p&gt;
&lt;p&gt;There is plenty of room for improvements, but now I'm stick with this patch: &lt;a href="https://git.sr.ht/~vp1981/pkgbuild/blob/master/logwatch/dovecot-2.4.patch." rel="nofollow"&gt;https://git.sr.ht/~vp1981/pkgbuild/blob/master/logwatch/dovecot-2.4.patch.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Also, there is this ticket: &lt;a href="https://sourceforge.net/p/logwatch/bugs/124/."&gt;https://sourceforge.net/p/logwatch/bugs/124/.&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Help with Debug Message</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/1df034d874/?limit=25#9ccc" rel="alternate"/><published>2025-08-21T06:31:05.542000Z</published><updated>2025-08-21T06:31:05.542000Z</updated><author><name>Andrew Myers</name><uri>https://sourceforge.net/u/andym/</uri></author><id>https://sourceforge.nete755edbc0d316175322c2e01a120a8ec7c64edf0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, I think it is a minor bug in the scrit:&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;&lt;span class="nt"&gt;if&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;$&lt;/span&gt;&lt;span class="nt"&gt;Debug&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;&amp;gt;=&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nt"&gt;5&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
&lt;span class="w"&gt;         &lt;/span&gt;&lt;span class="err"&gt;print&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;STDERR&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="n"&gt;DEBUG&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Found&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;Listening&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;on&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;port&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;22&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;line&lt;/span&gt;&lt;span class="err"&gt;\&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="err"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;

&lt;p&gt;So the message is hard coded into the debug.&lt;/p&gt;
&lt;p&gt;I can ignore it :)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>clam-update not working in logwatch 7.7</title><link href="https://sourceforge.net/p/logwatch/discussion/1115929/thread/4af80708f6/?limit=25#9f73" rel="alternate"/><published>2025-08-11T10:23:40.372000Z</published><updated>2025-08-11T10:23:40.372000Z</updated><author><name>Lukas M</name><uri>https://sourceforge.net/u/slyon23/</uri></author><id>https://sourceforge.netaa0683983a5506c8fbed26d9be4c4c3bc8016777</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;a class="user-mention" href="/u/bjorn1/profile/"&gt;@bjorn1&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;Especially:&lt;br/&gt;
"ClamAV update process started at Mon Jul 15 06:28:54 2024" vs "Mon Jul 15 06:28:54 2024 -&amp;gt; ClamAV update process started at Mon Jul 15 06:28:54 2024" (i.e. date prefix)&lt;/p&gt;
&lt;p&gt;I've created a bug report about this here: &lt;a href="https://sourceforge.net/p/logwatch/bugs/125/"&gt;https://sourceforge.net/p/logwatch/bugs/125/&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>