Dan Mashal wrote: >> >>Look at Mailman's logs. Run Mailman's bin/check_perms. Check the >>archiving settings, particularly ARCHIVE_TO_MBOX, in Defaults.py - >>mm_cfg.py. > >[EMAIL PROTECTED] mailman]# /usr/lib/mailman/bin/check_perms >Warning: Private archive directory is other-executable (o+x). > This could allow other users on your system to read private >archives. > If you're on a shared multiuser system, you should consult the > installation manual on how to fix this. >No problems found
Here's my best guess at this point. 1. the lists' archives are public. 2. when you migrated the archives, instead of copying the symlinks to archives/private/* directories from archives/public, you copied the actual linked directories. 3. Mailman is archiving just fine in archives/private/* as it should, but since archives/public/* is now the static structure you migrated, you don't see any changes. -- 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
