[Mailman-Users] List state db is corrupt

[John W Baxter]

At 12:37 -0800 10/29/2001, J C Lawrence wrote:
>On Mon, 29 Oct 2001 12:29:12 -0800
>John W Baxter <John> wrote:
>
>> At 11:12 -0800 10/29/2001, Dan Mick wrote:
>>> JC means "config_list", but I'm missing something; if you just
>>> want to back the files up, why don't you just back them up?  They
>>> don't need to be transmogrified on the way out and back in.
>
>> I think I'd feel more comfortable with a tool which takes a
>> (non-corrupt) Mailman database and writes it to (tab-delimited?
>> XML?) text for later conversion back.
>
>config_list does precisely that.

As I read config_list, it produces Python code which can be exec-ed in
order to rebuild the list configuration.

As such, config_list looks quite useful when needed.

My wish list item goes beyond that to include the membership, with the
various status options for each member.  Some sort of extension of
bin/list_members

For the moment, I can live with hoping that our backup process produces a
state not older than 24 hours before a list becomes corrupt...we haven't
had one become corrupt yet, but we just moved the middle-sized (~7000) list
from Majordomo a couple of weeks ago.  [It's performing much better with a
fairly "stock" Exim and Mailman than it did with a tuned Exim and
Majordomo...and there are opportunities for tuning this Exim instance.]

Wish list time frame for the above muttering is post-Mailman 2.1...I don't
see much reason to write anything for 2.0.6 at this point.

  --John

-- 
John Baxter   jwblist at olympus.net      Port Ludlow, WA, USA