[Mailman-Users] mailman mali list already created

Noah admin2 at enabled.com
Mon May 18 03:11:54 CEST 2009

Hi there,

I am migrating my old mailman system.   mailman thinks the mailman mail 
list is not created although it is as identified correctly by the 
newlist program.  What is going on here?

root at enabled:/usr/local/mailman# /etc/init.d/mailman start
  * Site list for mailman (usually named mailman) missing.
  * Please create it; until then, mailman will refuse to start.
root at enabled:/usr/local/mailman# bin/newlist mailman
Create a new, unpopulated mailing list.

Usage: bin/newlist [options] [listname [listadmin-addr [admin-password]]]


     -l language
         Make the list's preferred language `language', which must be a two
         letter language code.

     -u urlhost
         Gives the list's web interface host name.

     -e emailhost
         Gives the list's email domain name.

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

         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.

Every Mailman list has two parameters which define the default host name for
outgoing email, and the default URL for all web interfaces.  When you
configured Mailman, certain defaults were calculated, but if you are running
multiple virtual Mailman sites, then the defaults may not be appropriate for
the list you are creating.

You also specify the domain to create your new list in by typing the command
like so:

     newlist --urlhost=www.mydom.ain mylist

where `www.mydom.ain' should be the base hostname for the URL to this 
hosts's lists.  E.g. with this setting people will view the general list
overviews at http://www.mydom.ain/mailman/listinfo.  Also, www.mydom.ain
should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if
the email hostname to be automatically determined.

If you want the email hostname to be different from the one looked up by the
VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can 
`emailhost' like so:

     newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist

where `mydom.ain' is the mail domain name. If you don't specify 
emailhost but
urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will
be used for the email interface.

For backward compatibility, you can also specify the domain to create your
new list in by spelling the listname like so:

     mylist at www.mydom.ain

where www.mydom.ain is used for `urlhost' but it will also be used for
`emailhost' if it is not found in the virtual host table. Note that
'--urlhost' and '--emailhost' have precedence to this notation.

If you spell the list name as just `mylist', then the email hostname will be
taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as
defined in your Defaults.py file or overridden by settings in mm_cfg.py).

Note that listnames are forced to lowercase.

List already exists: mailman

More information about the Mailman-Users mailing list