The list creation can be done by two ways, according to listmaster needs :
WWSympa keeps logs of the creation and all modifications to a list as part of the list's config file (old configuration files are archived). A complete installation requires some careful planning, although default values should be acceptable for most sites.
Mailing lists can have many different uses. Sympa offers a wide choice of parameters to adapt a list behavior to different situations. Users might have difficulty selecting all the correct parameters to make the list configuration, so instead of selecting each parameters, list configuration is made with a list profile. This is an almost complete list configuration, but with a number of unspecified fields (such as owner e-mail) to be replaced by Sympa at list creation time. It is easy to create new list templates by modifying existing ones. (Contributions to the distribution are welcome...)
To create a list, some data concerning list parameters are required :
Moreover of these required data, provided values are assigned to vars being in the list creation template.
Then the result is the list configuration file :
On the Web interface, these data are given by the list creator in the web form. On command line these data are given by an xml file.
The xml file provides information on :
Here is an example of XML document that you can map with the following example of list creation template.:
<?xml version="1.0" ?> <list> <listname>example</listname> <type>my_profile</type> <subject>a list example</subject> <description/> <status>open</status> <shared_edit>editor</shared_edit> <shared_read>private</shared_read> <language>fr</language> <owner multiple="1"> <email>serge.aumont@cru.fr</email> <gecos>C.R.U.</gecos> </owner> <owner multiple="1"> <email>olivier.salaun@cru.fr</email> </owner> <owner_include multiple="1"> <source>my_file</source> </owner_include> <sql> <type>oracle</type> <host>sqlserv.admin.univ-x.fr</host> <user>stdutilisateur</user> <pwd>monsecret</pwd> <name>les_etudiants</name> <query>SELECT DISTINCT email FROM etudiant</query> </sql> </list> subject [% subject %] status [% status %] [% IF topic %] topics [% topic %] [% END %] visibility noconceal send privateoreditorkey Web_archive access public subscribe open_notify shared_doc d_edit [% shared_edit %] d_read [% shared_read %] lang [% language %] [% FOREACH o = owner %] owner email [% o.email %] profile privileged [% IF o.gecos %] gecos [% o.gecos %] [% END %] [% END %] [% IF moderator %] [% FOREACH m = moderator %] editor email [% m.email %] [% END %] [% END %] [% IF sql %] include_sql_query db_type [% sql.type %] host [% sql.host %] user [% sql.user %] passwd [% sql.pwd %] db_name [% sql.name %] sql_query [% sql.query %] [% END %] ttl 360
The XML file format should comply with the following rules :
See chapter 17, page
This way to create lists is independent of family.
Here is a sample command to create one list :.
sympa.pl -create_list -robot my.domain.org-input_file /path/to/my_file.xml
The list is created under the my_robot robot and the list
is described in the file my_file.xml. The XML file is
described before, see 16.1.2, page .
By default, the status of the created list is open.
The list creator has to choose a profile for the list and put its name in the XML element <type>.
List profiles are stored in /usr/local/sympa-os/etc/create_list_templates or in /usr/local/sympa-os/bin/etc/create_list_templates (default of distrib).
You might want to hide or modify profiles (not useful, or dangerous for your site). If a profile exists both in the local site directory /usr/local/sympa-os/etc/create_list_templates and /usr/local/sympa-os/bin/etc/create_list_templates directory, then the local profile will be used by WWSympa.
The management of mailing lists is based on a strict definition of privileges which pertain respectively to the listmaster, to the main list owner, and to basic list owners. The goal is to allow each listmaster to define who can create lists, and which parameters may be set by owners.
Listmasters have all privileges. The listmaster is defined in sympa.conf and others are defined at the virtual robot level. By default, newly created lists must be activated by the listmaster. List creation is possible for all intranet users (i.e. : users with an e-mail address within the same domain as Sympa). This is controlled by the create_list authorization scenario.
List rejection message and list creation notification message are both templates that you can customize (list_rejected.tt2 and list_created.tt2).
This is defined by the create_list sympa.conf parameter (see 6.1.15,
page ). This parameter refers to a create_list authorization scenario.
It will determine if the create list button is displayed and if it requires
a listmaster confirmation.
The authorization scenario can accept any condition concerning the [sender] (i.e. WWSympa user), and it returns reject, do_it or listmaster as an action.
Only in cases where a user is authorized by the create_list authorization scenario will the "create" button be available in the main menu. If the scenario returns do_it, the list will be created and installed. If the scenario returns "listmaster", the user is allowed to create a list, but the list is created with the pending status, which means that only the list owner may view or use it. The listmaster will need to open the list of pending lists using the "pending list" button in the "server admin" menu in order to install or refuse a pending list.
# Do not allow the public_anonymous profile public_anonymous hidden * read
For each parameter, you may specify (via the /usr/local/sympa-os/etc/edit_list.conf configuration file) who has the right to edit the parameter concerned ; the default /usr/local/sympa-os/bin/etc/edit_list.conf is reasonably safe.
Each line is a set of 3 field <Parameter> <Population> <Privilege> <Population> : <listmaster|privileged_owner|owner> <Privilege> : <write|read|hidden> parameter named "default" means any other parameter
There is no hierarchical relation between populations in this configuration file. You need to explicitely list populations.
Eg: listmaster will not match rules refering to owner or privileged_owner
examples : # only listmaster can edit user_data_source, priority, ... user_data_source listmaster write priority owner,privileged_owner read priority listmaster write # only privileged owner can modify editor parameter, send, ... editor privileged_owner write send owner read send privileged_owner,listmaster write # other parameters can be changed by simple owners default owner write
Privileged owners are defined in the list's config file as follows :
owner email owners.email@foo.bar profile privileged
The following rules are hard coded in WWSympa :
Sympa aims to define two levels of trust for owners (some being entitled simply to edit secondary parameters such as "custom_subject", others having the right to manage more important parameters), while leaving control of crucial parameters (such as the list of privileged owners and user_data_sources) in the hands of the listmaster. Consequently, privileged owners can change owners' e-mails, but they cannot grant the responsibility of list management to others without referring to the listmaster.
Concerning list edition in a family context, see 17.2.8, page