I wrote: > > First question -- do we really need the zipped up copy, while the > > unzipped version is in the directory? Are there any local settings we > > can do to optimize space until we've moved to the new machine? >
and in response: On Wed, 2006-08-16 at 14:02 -0700, William Yardley wrote: > My understanding is that this copy is just to make it easy for people to > download a compressed archive of the mbox file. > > See: > GZIP_ARCHIVE_TXT_FILES = No > > in Defaults.py > > So you sould see if GZIP_ARCHIVE_TXT_FILES is set in mm_cfg.py. > > After disabling that, I think you should just be able to remove the .gz > files. Thanks. This worked, with the exception that rather than setting that variable (which seemed to be set to 'No' by default) I just had to comment out the cron job "nightly_gzip" (same effect). Now I have one other related question. The archives directories have the mbox file of the form: mailman/archives/private/<listname>.mbox/<listname>.mbox This file seems to grow indefinitely, and is paralleled by the various *.txt files broken down by month. We'd like to remove messages older than a certain date. Reading the Site Administrator Documentation the best I can infer is that the way to do this would be edit the *mbox file and run arch to rebuild the html archives. Is this true? Will "arch" remove the *.txt files corresponding to the deleted messages from the *mbox? Larry ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
