-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jon Carnes wrote: > That would work. I would also delete the aliases and with the web-admin > mark the list as private.
Wouldn't doing so prevent access to the archives? I read Carl's message to mean that he wanted the list archives to remain accessible. If the archives are public, this is really simple with rmlist. If they're private, I'm curious how that'll work, as I can't recall ever having done it. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ============================================================================ Things in our country run in spite of government, not by aid of it. -- Will Rogers -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+X5Lvuv+09NZUB1oRAvYqAKC65g26+zBLJeb93LsQJ0i3xV4VKgCgwlmK 0qMHI6/sEi6n31IWpKkrfyM= =eY5z -----END PGP SIGNATURE----- ------------------------------------------------------ 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org