On Wed, May 9, 2012 at 12:20 PM, Mark Sapiro <m...@msapiro.net> wrote:
> I can't diagnose what the real issue was without knowing the ownership > and permissions before the change Thank you. This discussion has increased my understanding and better prepared me to deal with these issues after future upgrades. I know what to look for now. We also have a test box running an identical installation of Mailman. If we can reproduce this I'll let you know. (I can't go back and check permissions on the test box now, however, because I actually did these steps on that box first, then implemented them on the production box -- before I noticed the loss of access to the archives. So both boxes have the same permissions/ownerships at this point.) The good news is that everything is working. ------------------------------------------------------ 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
