Derzeit gibt es einen Bug im Zusammenspiel mit mailman und logrotate. Wenn man logrotate in Version 3.8.0 oder höher installiert, spuckt mailman beim Aufruf des logrotate Jobs folgende Fehlermeldung aus:

/etc/cron.daily/logrotate:
error: skipping "/var/log/mailman/vette" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/error" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/bounce" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/mischief" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/digest" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/subscribe" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/post" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/qrunner" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/fromusenet" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/locks" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/smtp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mailman/smtp-failure" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

und bzw. oder

/etc/cron.daily/logrotate:
Traceback (most recent call last):
  File "/usr/lib/mailman/bin/mailmanctl", line 555, in <module>
    main()
  File "/usr/lib/mailman/bin/mailmanctl", line 341, in main
    check_privs()
  File "/usr/lib/mailman/bin/mailmanctl", line 296, in check_privs
    os.setgroups(groups)
OSError: [Errno 1] Operation not permitted

Lösen kann man dieses Problem in dem man ein „su list list“  in /etc/logrotate.d/mailman hinzufügt und „mailmanctl“ mit dem Flag „-u“ aufruft.

Hier ein Beispiel:

/var/log/mailman/digest {
su list list
monthly
missingok
create 0664 list list
rotate 4
compress
delaycompress
sharedscripts
postrotate
[ -f ‚/var/run/mailman/mailman.pid‘ ] && /usr/lib/mailman/bin/mailmanctl -u -q reopen || exit 0
endscript
}

Was denkst du?


Zustimmung zur Datenspeicherung lt. DSGVO