[Mailman-Developers] What to do with a corrupt config.db?

[Aaron D. Turner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


It seems all the config.db's (and their .last's) for all my lists are now
corrupt.  At least check_db says so.  Since there doesn't seem to be
anyway to fix this, perhaps there is a way to extract the email
addresses/passwords for the lists so I can recover?

I'm more than willing/able to write a perl script to parse it out, if I
just knew the file format (though i can prolly get the email addresses out
without much difficulty).

Anyone have any thoughts/suggestions?

Thanks.

- -- 
Aaron Turner <aturner@pobox.com|synfin.net|linuxkb.org>  URI:www.synfin.net
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety. -- Benjamin Franklin

pub 1024D/F86EDAE6  Sig: 3167 CCD6 6081 0FFC B749  9A8F 8707 9817 F86E DAE6
All emails by me are PGP signed; a lack of a signature indicates a forgery.
I have retired my PGP 2.6.2 key: FBE1 CEED 57E4 AB80  596E 60BF 451B 20E8
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Public key at: http://www.synfin.net/aturner/pgpkey.asc

iEYEARECAAYFAju6ALQACgkQhweYF/hu2uZ8wACeMzlq++UjA3zuMhSEvsc9McUp
HqcAn0gD4ywicbKxyRF4/Ihg2T6bq45I
=uSaH
-----END PGP SIGNATURE-----