similar to: dovecot logs to audit.log not to maillog

Hello, now I have done this: under http://wiki.dovecot.org/Logging?highlight=(logging) Rotating Logs is the following string ----------------------- /bin/kill -USR1 `cat /var/run/dovecot/master.pid 2>/dev/null` 2> /dev/null || true ------------------------ This string I have insert in /etc/logrotate.d/syslog under the lines: postrotate /bin/kill -HUP `cat /var/run/syslogd.pid

Hi, I'm trying to figure out which process is rotating my maillog every Sunday at 4:03 am. This happens on all of my centos 4 boxes. AFAICT, logrotate is not running. This is from a fairly minimal install, so I'm assuming this is a default process. --- [root at penguin ~]# ls -l /var/log/maill* -rw------- 1 root root 230603836 Sep 27 16:30 /var/log/maillog -rw------- 1 root

Dear Friends, How I restart logrotate ? Because file /var/log/maillog doesn't rotate log. Thanks Adriano

Hi, I want to create a new log /var/log/maillog for postfix each day and so i created a new logrotate config for the log and removed it from /etc/logrotate.d/syslog. ~]# cat /etc/logrotate.d/maillog /var/log/maillog { daily rotate 31 start 1 compress create 0600 root postrotate /etc/init.d/postfix reload > /dev/null endscript } After

When logs (e.g. /var/log/maillog) are rotated (e.g. to /var/log/maillog-YYYYMDD) is there a way via systemd or whatever to assign read permission to a specific group? Right now, for example - ls -l maillog* -rw------- 1 root root 3105240 Mar 13 22:04 maillog -rw------- 1 root root 1079031 Feb 24 04:39 maillog-20190224 -rw------- 1 root root 7237640 Mar 1 12:59 maillog-20190228 -rw------- 1

My /var/log/maillog was getting pretty big because of lots of testing and re-configuring I've been doing lately with both Dovecot and Postfix. I figured just remove /var/log/maillog and it would be re-created. It wasn't--not by Dovecot, not by Postfix. I had to manually create a new one, put one character in it, save it, properly secure it with chmod, and then Dovecot (and postfix)

So, the question is, why can I rotate the log manually, but cron returns a permission error? Do I need to tell cron to run it as sudo or something like that? Ethon > On Nov 17, 2017, at 2:29 AM, Tom Hendrikx <tom at whyscream.net <mailto:tom at whyscream.net>> wrote: > > Hi, > > > Your crontab should normally mail you error output. But you can also run > the

I have recently noticed that my dovecot-deliver.log is huge and wanted to start rotating it. So a couple of questions: 1. Can the dovecot-deliver.log be combined with the maillog, that gets rotated weekly? If it can be done, is it advisable? Since the inception of this particular server, the log file has been located in the /home/vmail directory. Is there a reason it shouldn?t be located in

That doesn?t seem to work either. Where do I find logs for log rotation to see the reason it failed? Ethon > On Nov 16, 2017, at 7:53 PM, Bill Shirley <bill at KnoxvilleChristian.org <mailto:bill at KnoxvilleChristian.org>> wrote: > > I believe you need a 'create' statement to set the permissions. Here > is an example for mariadb: >

Hi there, after banging my head against a wall for a bit I got more indepth with dovecot and am now much more knowledgeable about the system than before. But I still have two problems: 1.) For some reason my dovecot doesnt log correctly. I put debug_log to -1 and expected to see logs flooding in in my syslog. When I try to log in via telnet over imap and the login succeeds it loggs correctly.

Anyone having problems with logrotate and CentOS 5.4? Although I have /etc/logrotate.d/mail (contents below) to rotate my maillog file, it fails to do it automatically: /var/log/maillog { compress dateext maxage 365 rotate 60 size=+1024k missingok postrotate /etc/init.d/MailScanner restart endscript } ++++++++++++++++++++++++++++ logrotate.conf:

Hi, I am testing dovecot with Outlook Mobile 5 (OM5), which is currently not working. OM5 connects, says "NOOP" and "CAPABILITY", does login correctly and simply loggs out after that telling the user that it could not download any messages. When I put an imapproxy[0] in front of dovecot, OM5 works perfectly well. That leads me to the thought, that something in the way dovecot

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but only clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K errro message. But if the same user loggs on on a client machine with W2K SP1 all things are ok.

I have a problem in that at first all my log files were dated 12-31-1969 and logrotate has: # more /var/lib/logrotate.status logrotate state -- version 2 "/var/log/yum.log" 1969-12-31-20:26:1 "/var/named/data/named.run" 1969-12-31-20:26:1 "/var/log/httpd/error_log" 2015-8-27-4:43:1 "/var/log/wtmp" 1969-12-31-20:26:1 "/var/log/chrony/*.log"

Removes the delaycompress line so that every rotation is compressed. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- logrotate/ovirt-logrotate.conf | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/logrotate/ovirt-logrotate.conf b/logrotate/ovirt-logrotate.conf index 8747f59..8b89a2d 100644 --- a/logrotate/ovirt-logrotate.conf +++

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K error message. But if the same user loggs on on a client machine with W2K SP1 all things are ok. In

Thank you. And what user/group/file perms does your dovecot.log file have? - Michael On 19/03/17 13:43, Richard wrote: > >> Date: Sunday, March 19, 2017 13:32:57 +1300 >> From: Michael Heuberger <michael.heuberger at binarykitchen.com> >> >> Hello guys >> >> Having headaches here how to make logrotation for dovecot log files >> work. Having

I got the fail2ban from epel. There were a number of issues relating to using a log file... logwatch was looking for both fail2ban and fail2ban.log logrotate file fail2ban added looked for fail2ban.log and then reset itself to syslog fail2ban itself went to syslog, over riding its fail2ban.log. took a while, but I use /var/log/fail2ban now, that finally worked through logrotates and logwatch.

Well, I tried the same but it didn't work. Setting my dovecot.log to 600 with root:root is breaking my mail system. I am then unable to receive and open emails. Had to apply an ugly hack /var/log/dovecot*.log { su syslog syslog create 666 syslog syslog rotate 10 ... } Like that anyone who wants to access/write to it, can do it and all works. That's my

http://bugzilla.mindrot.org/show_bug.cgi?id=956 Summary: Syslog do not tell you when user loggs out. Product: Portable OpenSSH Version: 3.8p1 Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: olle at