URL:
<http://gna.org/bugs/?7302>
Summary: Sometimes, sv_mailman fails to create lists
Project: Savane
Submitted by: yeupou
Submitted on: mercredi 04.10.2006 à 08:21
Category: Backend
Priority: A - Later
Severity: 3 - Normal
Status: Need Info
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Release: 2.0
Planned Release:
_______________________________________________________
Details:
Sometimes, sv_mailman fails to create lists. In the logs, we get
"Create a new, unpopulated mailing list.
Usage: /usr/sbin/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:
[EMAIL PROTECTED]
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.
The list admin address need to be a fully-qualified address, like
[EMAIL PROTECTED], not just owner.
The list password cannot be empty
Configure a list from a text file description.
Usage: config_list [options] listname
Options:
--inputfile filename
-i filename
Configure the list by assigning each module-global variable in the
file to an attribute on the list object, then saving the list. The
named file is loaded with execfile() and must be legal Python code.
Any variable that isn't already an attribute of the list object is
ignored (a warning message is printed). See also the -c option.
A special variable named `mlist' is put into the globals during the
execfile, which is bound to the actual MailList object. This lets
you
do all manner of bizarre thing to the list object, but BEWARE!
Using
this can severely (and possibly irreparably) damage your mailing
list!
--outputfile filename
-o filename
Instead of configuring the list, print out a list's configuration
variables in a format suitable for input using this script. In this
way, you can easily capture the configuration settings for a
particular list and imprint those settings on another list.
filename
is the file to output the settings to. If filename is `-', standard
out is used.
--checkonly
-c
With this option, the modified list is not actually changed. Only
useful with -i.
--verbose
-v
Print the name of each attribute as it is being changed. Only
useful
with -i.
--help
-h
Print this help message and exit.
The options -o and -i are mutually exclusive.
No such list "omeo-devel""
I guess the "No such lists" comes from the list configuration that fails
obviously because the list was not created.
I found no clues why this list werent created.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?7302>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
