[Mailman-Users] Safe Archive Clean

[Mark Sapiro]

Young, Darren wrote:

>Couple questions on archiving.
>
>First, have some lists that archives exist for that I need to remove. We
>don't support archiving so I need to blast them. What's the "safe" way
>to do this?

Set archive_private to 'private'. This should delete the
archives/public/<listname>/ directory if there was one. Then you can
delete everything in archives/private/<listname>, but it would be
safest to have an index.html file that just says there is no archive.
The satanard one is based on templates/<lang>/emptyarchive.html

>On that note (we don't support archiving), I've disabled archives on all
>lists on our server (via withlist), have set DEFAULT_ARCHIVE = Off &
>ARCHIVE_TO_MBOX to -1 in Defaults.py. Additionally, I removed the
>archive option from the UI via Defaults.py as well.
>
>Now, what I'm finding is that if a list has content filtering disabled,
>or set to allow other MIME types through (such as HTML) and if a member
>is of type digest and they have the plain option enabled for digests,
>they receive a message in their digest with a URL of where they can see
>a copy of the original message. The URL included has a pipermail address
>in it. On the server, the file was placed in that directory however I
>have pipermail disabled (since we don't support archives). Any way to
>disable this part or do I just need to wipe those archived files?

I'm not sure what you want here. If you set archive_private to
'private', the URL will be to the private archive location rather that
the pipermail location.

For HTML parts see the description of ARCHIVE_HTML_SANITIZER in
Defaults.py.

--
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan