Andrew Watson wrote: > >1) on the old server, all files in /usr/local/mailman/lists and >/user/local/mailman/archives have group mailman, but group wheel on the >new server.
This needs to be fixed. Everything needs to be Mailman's group >2) on the old server, all archives/public files are owned by www, but on >the new server by root. > There should be no archives/public files at all; only symlinks. Ownership of symlinks is irrelevant. If the old server had actual files in archives/public rather than symlinks, the best recourse may be to rebuild the archive for those lists with bin/arch --wipe >3) on the old server, all .mbox files in archives/private are owned by >www, but on the new server by root. This doesn't matter. It's the group that's important, not the owner. >4) on the old server, all files in lists are owned by www, but on the See 3. >Should I correct all owner and group states to match the old server? >From previous posts, I gather that owner is not important but that >group MUST be "mailman". First, run bin/check_perms -f as root on the new server until it either fixes everything or gets to a "no change" point. That may be enough, but if there are files left that aren't in Mailman's group, you can fix thiose by hand. -- Mark Sapiro <m...@msapiro.net> 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://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