Thanks for the replies so far. The host has reset the permissions. No digest was sent out today, which is a bit strange. The next run will show if everything's fine now...
Jan -----Ursprüngliche Nachricht----- Von: Mark Sapiro [mailto:m...@msapiro.net] Gesendet: Dienstag, 11. Dezember 2012 12:34 An: Stephen J. Turnbull; Jan Krohn Cc: Mailman-Users@python.org Betreff: Re: [Mailman-Users] Digest growing to infinity It certainly seems that Mailman's cron/senddigests is not removing the lists/LISTNAME/digest.mbox file after creating the digest. I doubt however that check_perms will find a problem. The lists/LISTNAME/ directory must be writable by Mailman as it also contains the list configuration files and every time the list is updated for a post or anything else, a new temporary config file is created and then the existing files all have their names changed so that the config becomes the backup and the new temporary file becomes the config, all of which requires write access to the directory. My first thought is that cron/senddigests is not being run as the Mailman user, but that seems unlikely as other lists work. The host also needs to check Mailman's error log which should contain clues. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
