[Qmail] Scavange stopps maillog - cron command to activate authentication

[Kloxo-DR]

Hello,

Before the forum got wiped off, I had placed message on scavange deactivating qmail processes.

I found from # qmailctl stat that - for some unknown reasons - authlib/log, send/log and smtp-ssl/log was down, mostlikely after scavange. This affected authentication as well.

Now I have inserted in root crontab to run every five minutes, as root, the following:

svc -u /var/qmail/supervise/authlib/log
svc -u /var/qmail/supervise/send/log
svc -u /var/qmail/supervise/smtp-ssl/log

This works and helps.

[Kloxo-DR]

As rsyslog stops after scavange, this would better:

/etc/yum.repos.d/
http://rpms.adiscon.com/v7-stable/rsyslog.repo
yum update

[Kloxo-DR]

After the scavange time is completed, rsyslog stops.

Thus, there is no maillogging thereafter.

This can be regained by the following command in cron:

qmailctl stop
qmailctl start

Reminder: As Mustafa said, service qmail restart is not equal to service qmail stop and service qmail start, one must execute the above commands.

Only then all the services from qmail will actually stop and restart.

Unfortunately, as the maillog stops, many other associated functions stops as well.

Since I have CSF firewall and login detection installed based on maillog, the entire firewall activity stops anfetr scavange is run.

Hence, Mustafa, I request to you to investigate this issue in the area of scavange as well as the issue of qmail stop/start everywhere.