[Mailman-Developers] Creation/deletion of liststhrough-the-web

Ben Burnett benwa@ocentrix.com
Wed, 9 May 2001 16:21:53 -0700

------- Original Copy -------
>Subject: Re: [Mailman-Developers] Creation/deletion of
>Date: 05/09/2001 3:23 PM
>From: Ron Jarrell <jarrell@vt.edu>
>To: barry@digicool.com (Barry A. Warsaw), "Jay R. Ashworth"
>Cc: mailman-developers@python.org

>>The list creation message is always sent currently.  Does
it make
>>sense to be able to inhibit that?
>Yes.  I currently manually go in and fix some things that
just can't be set
>from defaults easily before letting the admin know. 
Ideally I'd like a button
>for "(re)send list creation message now", because what I do
is run newlist,
>hit ctl-z, go off and make my changes, fg it, and let it
send the list message...

FWIW I do sort of the same thing.  I have hacked newlist to
accept another option as described below.

[mailman@mail riders_connection]$ ./bin/newlist
Create a new, unpopulated mailing list.

Usage: %(PROGRAM)s [options] listname listadmin-addr


        Normally the administrator is notified by email
(after a prompt) that
        their list has been created.  This option suppresses
        notification and the prompting.

    -s file
        Append the email that is sent to the administrator
of the new list
        to file.  This is in addition to sending the email
to the administrator
        unless -q is used.

    -o file
        Append the alias setting recommendations to file, in
addition to
        printing them to standard output.

        Print this help text and exit.

You can specify as many of the arguments as you want on the
command line:
you will be prompted for the missing ones.

Note that listnames are forced to lowercase.

[mailman@mail riders_connection]$

a patch for this against 2.0.3 is attached if anyone is