[Mailman-Users] Problem using "newlist"

[Jean Berthold]

Hello everybody,

I have installed the tools required by mailman: python and apache.
Then, I installed mailman without visible errors.

At this moment, I try to create my first list, unsuccessfully ...

The server:
--------------
$ uname -a
SunOS atlanta 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10

$ id
uid=1003(mailman) gid=103(mailman)

$ mailmanctl start
Starting Mailman's master qrunner.
$ ps -ef | grep mailman
 mailman 15485 15482  3 16:29:09 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
 mailman 15487 15482  3 16:29:09 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
 mailman 23264 23262  0   Jan 07 pts/5    0:00 -ksh
 mailman 14567 23264  0 16:38:35 pts/5    0:00 vi Defaults.py
 mailman 15482     1  0 16:29:09 ?        0:00 /usr/local/bin/python
mailmanctl start
 mailman 14028 13935  0   Jan 07 pts/6    0:00 -ksh
 mailman 15483 15482  3 16:29:09 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
 mailman 15488 15482  3 16:29:10 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
 mailman 14489 14465  0   Jan 07 pts/7    0:00 -ksh
 mailman 15486 15482  3 16:29:09 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
 mailman 15484 15482  3 16:29:09 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
 mailman 15489 15482  3 16:29:10 ?        0:01 qrunner
/usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
 mailman 15491 14489  0 16:29:14 pts/7    0:00 grep mailman

$ ps -ef | grep nobody
  nobody 14424 14423  0   Jan 07 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 15270 14423  0 10:52:29 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 14426 14423  0   Jan 07 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 14428 14423  0   Jan 07 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 14425 14423  0   Jan 07 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 15272 14423  0 10:52:30 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 14452 14423  0   Jan 07 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 15271 14423  0 10:52:30 ?        0:00
/usr/local/apache2/bin/httpd -k start
  nobody 14427 14423  0   Jan 07 ?        0:00
/usr/local/apache2/bin/httpd -k start

The hostname of my mailman server:
------------------------------------------
mailman at atlanta # cat /etc/hosts
#
# Internet host table
#
127.0.0.1       localhost
172.16.16.2     atlanta atlanta.eos.elro loghost



Below, are the error messages:
------------------------------------
$ newlist test mailman at atlanta.eos.elro testlit
Create a new, unpopulated mailing list.

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

Options:

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

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

    -h/--help
        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 can specify the domain to create your new list in by spelling the
listname
like so:

    mylist at www.mydom.ain

where `www.mydom.ain' should be the base hostname for the URL to this
virtual
hosts's lists.  E.g. with is 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.
It
will be looked up to give the email hostname.  If this can't be found,
then
www.mydom.ain will be used for both the web interface and the email
interface.

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.

Illegal list name: test at atlanta
$

Do I need to specify an URL like www.... in my Defaults.py or can I keep
this current configuration:
# because otherwise the default mappings won't be correct.
DEFAULT_EMAIL_HOST = 'atlanta'
DEFAULT_URL_HOST = 'atlanta'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'

I cannot found where is my error, could you help me ?

Thanks by advance and have a nice day


--
________________________________

Jean Berthold
EOS - energie ouest suisse
Chemin de Mornex 10 , CP 570
CH-1001 Lausanne , Switzerland
Tel. : +41 (0)21 341 24 58
Fax  : +41 (0)21 341 20 49
E-Mail : jean.berthold at eos-gd.ch
________________________________



                          ...Unix is like a wigwam - no windows, no
gates, apache inside...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/mailman-users/attachments/20030108/e26aa5a4/attachment.htm