1 Topic by nerdtron09

  • nerdtron09
  • Member
  • Offline
  • Registered: 2013-06-10
  • Posts: 57

Topic: Cron Logwatch

==== Required information ====
- iRedMail version: 0.8.4
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: Ubuntu 12.04
- Related log if you're reporting an issue: postmaster logwatch email
====

In the daily Logwatch email to the postmaster account.
Is this OK, or I should do something about it?

--------------------- Cron Begin ------------------------


**Unmatched Entries**
INSECURE MODE (mode 0600 expected) (crontabs/root)
INSECURE MODE (mode 0600 expected) (crontabs/amavis)

---------------------- Cron End -------------------------

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,091

Re: Cron Logwatch

Did you check file permission of files under /var/spool/cron/crontabs/? They should be set to 0600, so that other users cannot view their file content.

3 Reply by nerdtron09 (edited by nerdtron09 2013-07-05 17:53:51)

  • nerdtron09
  • Member
  • Offline
  • Registered: 2013-06-10
  • Posts: 57

Re: Cron Logwatch

root@mail:/var/spool/cron/crontabs# ll
total 16
drwx-wx--T 2 root crontab 4096 Jul  3 09:26 ./
drwxr-xr-x 5 root root    4096 Jun 20 19:49 ../
-rw------- 1 root root     290 Jul  3 09:25 amavis
-rw------- 1 root root     293 Jul  3 09:26 root


--------------

I change the permissions to 0600. I didn't have this problem on my test email server install before.