similar to: Is there a tool similar to pflogsumm for Dovecot?

I'm trying to get usable reports out of logwatch on this new system. Looks like the reports are running in an 'unformatted' mode under Postfix/Amavisd. I found a couple of programs, postfix-logwatch and amavisd-logwatch. These sound promising. I am running Amavisd as the frontend to Postfix. Is anybody running either of these as a logwatch filter? If so, is it repetitive to run

I've just ported a largeish procmail script across to sieve and want to get to use wildcards in filing mail and can't seem to get regex to work. The script starts nicely with: > require ["fileinto","regex","envelope","vacation","regex"]; and a bit down these few lines comes into play: > elsif header :regex "From"

Hi List, Centos 5(.2) ships with dovecot-1.0.7-2.el5 and logwatch-7.3-6.el5 However the shipped logwatch is not aware of dovecot 1.x meaning none of the log entries (var/log/maillog) are processed at all. Should I file a bug report on this? Upstream? cheers Henry

Howdy all, Question for anyone. I have centos 5.x on my server. Everyday I get a logwatch sent to my mailbox. I usually check every couple weeks and this time I got a surprise... Up until may 15th, the watch started with cron begin/ cron end and then went to http begin/end.... May 16th had the selinux (which I have disabled) and dovecot listings above the http begin. Cron was absent.

At what level does Dovecot log to syslog? UW-IMAP uses local6.debug to log to syslog, but it doesn't seem that dovecot does the same.. (the file I defined for UW-IMAP's output hasn't received anything since I moved over to Dovecot? Also, has anyone managed to get LogWatch and Dovecot to play nicely together? I noticed that LogWatch no longer gives any statistics on the imap

On my new Haswell-based machines, I am occasionally seeing entries like the following in /var/log/messages: kernel: [Hardware Error]: Machine check events logged (I would not have even noticed them, except that they get flagged by logwatch.) These messages always occur alone, and don't seem to have a corresponding entry in any other log file in /var/log. How can I get more info about these

On Wed, May 25, 2016 4:31 pm, Philip McGaw wrote: > Did user historically have POP set up? Philip, thanks no, not for a long time, IMAP/143/StartTLS on old laptop > If you still have access to the old laptop set up imap and move the > emails back. yes, I have old laptop here. sorry, not sure how to, is that inside TBird, or how ? (not very familiar with TBird...) >> another OT:

On Thu, 2019-11-21 at 13:44 +0100, Adrian van Bloois wrote: > I wonder if there is a script to analyze logfiles for llogwatch and > sshguard? > Anyone knows? You can take an existing script, for another piece of software reported by Logwatch, retain the beginning and ending parts, and create your own version. The completed script should be placed in /etc to ensure it is not

On Sat, September 19, 2015 06:51, Tony Mountifield wrote: > In article > <d0000782c236fbee71045dad24a43def.squirrel at webmail.harte-lyne.ca>, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >> After some experimenting I have observed that overriding settings from >> /usr/share/logwatch/default.conf/logwatch.conf in >> /etc/logwatch/conf/logwatch.conf does not

Migrated a 1.0.2 server to 2.0.16 (same old box). IMAP seems working Ok. POP3 give problems with some clients (Outlook 2010 and Thunderbird reported). Seems authentication problem Below my doveconf -n (debug enbled, but no answer found to the problems) Any hints? Thanks, P. # doveconf -n # 2.0.16: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with:

I having a problem where Logwatch is not showing any events from the /var/log/secure log file. When I run logwatch --print --range today --service sshd --detail 10 --debug 10 the end result shows this: ... LogFiles that will be processed: [0] = secure [1] = messages Made Temp Dir: /var/cache/logwatch/logwatch.sOga48bL with tempdir export LOGWATCH_DATE_RANGE='today' export

http://bugzilla.mindrot.org/show_bug.cgi?id=1216 Summary: Warn via Logwatch when sshd PermitRootLogin is in effect Product: Portable OpenSSH Version: 4.3p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org

> Date: Sunday, April 09, 2017 08:36:17 -0400 > From: Robert Moskowitz <rgm at htt-consult.com> > > Logwatch is installed, and I am assuming by how empty /etc/logwatch > is that it is running from defaults, which I find in > /usr/share/logwatch/default.conf/services > > I want to customize ONE service. dovecot. > > Do I copy

On Mon, September 14, 2015 21:28, Always Learning wrote: > > On Mon, 2015-09-14 at 14:51 -0400, James B. Byrne wrote: > >> The Logwatch imapd service script distributed with CentOS-6 does not >> generate anything when I run logwatch --service all on a cyrus-imapd >> host. Is this expected behaviour? Is there a separate script for >> cyrus-imapd or are their

After some experimenting I have observed that overriding settings from /usr/share/logwatch/default.conf/logwatch.conf in /etc/logwatch/conf/logwatch.conf does not produce consistent results. For example, if I replace the default detail configuration in etc/logwatch/conf/logwatch.conf with: Detail = High It does indeed change the level of detail from the default Low set in

Logwatch is installed, and I am assuming by how empty /etc/logwatch is that it is running from defaults, which I find in /usr/share/logwatch/default.conf/services I want to customize ONE service. dovecot. Do I copy /usr/share/logwatch/default.conf/services/dovecot.conf to /etc/logwatch/conf/services and edit it there, or do I have to copy ALL default.conf/services/* there and modify

CentOS 6 (amd64) up to date with latest security / bug fixes. The logwatch reports come in plain text even though the config states HTML. <begin /etc/logwatch/conf/logwatch.conf> mailer = "/usr/sbin/sendmail -t" TmpDir = /tmp MailFrom = logwatch at example.com MailTo = admin1 admin2 admin3 Range = yesterday Detail = Medium HostName = www.example.com Print = No Output = mail

>>> >>> --------------------- sendmail Begin ------------------------ >>> >>> STATISTICS >>> ---------- >>> >>> Bytes Transferred: 5241 >>> Messages Processed: 2 >>> Addressed Recipients: 2 >>> >>> ---------------------- sendmail End ------------------------- >>>

>-----Original Message----- >From: Ama Kalu [mailto:ama.kalu@cwlgroup.net] >Sent: Wednesday, November 19, 2003 9:07 PM >To: ''Tom Eastep'' >Subject: RE: [Shorewall-users] logwatch > >Thanks Tom and Andrew, > >About 2 months ago, I setup the most current (at the time) version of >logwatch, it required a service filter for IPTABLES which I did not have

After the upgrade to CentOS 5.9, all my CentOS 5 installations report only "Unmatched Entries" in the "yum" section of their daily logwatch mails. It seems the filter script /usr/share/logwatch/scripts/services/yum got broken: --------8<--------8<--------8<--------8<--------8<--------8<--------8< [root at dns01 ~]# /usr/sbin/logwatch --print --service yum