Ki Song wrote: >Scratch the last comment. Apparently, the config.pck and other pck files are >recreated every time the cron runs. The problem is that when this file is >recreated, the permissions are such that mailman cannot modify that file. >For example, my config.pck file for all the lists on my mailman server are >automatically created with permissions with user apache. However, mailman is >not an authorized owner. > >What should I do? Should I try and make the config.pck file default to >mailman ownership?
Mailman's access permissions are based on group, not user. Everything should be group owned by 'mailman', and the group should have read and write permission, and the crontab should be installed for user 'mailman' which should be in the 'mailman' group so that the cron jobs run as group mailman. Whether the user who owns files is mailman or root or apache or some combination of these and others should be irrelevant. See <http://www.list.org/mailman-install/node9.html>. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
