Sophie

Sophie

distrib > Mandriva > 8.2 > i586 > media > contrib > by-pkgid > 968fb36a1d13190d5ed9d2ee3bf64b87 > files > 79

sympa-3.2.1-4mdk.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<!--Converted with LaTeX2HTML 99.2beta8 (1.42)
original version by:  Nikos Drakos, CBLU, University of Leeds
* revised and updated by:  Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
  Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>10. Creating and editing mailing using the web</TITLE>
<META NAME="description" CONTENT="10. Creating and editing mailing using the web">
<META NAME="keywords" CONTENT="sympa">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="LaTeX2HTML v99.2beta8">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="sympa.css">

<LINK REL="next" HREF="node12.html">
<LINK REL="previous" HREF="node10.html">
<LINK REL="up" HREF="sympa.html">
<LINK REL="next" HREF="node12.html">
</HEAD>

<BODY TEXT="#000000" BGCOLOR="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html681"
  HREF="node12.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A> 
<A NAME="tex2html675"
  HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A> 
<A NAME="tex2html669"
  HREF="node10.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A> 
<A NAME="tex2html677"
  HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A> 
<A NAME="tex2html679"
  HREF="node17.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html682"
  HREF="node12.html">11. List configuration parameters</A>
<B> Up:</B> <A NAME="tex2html676"
  HREF="sympa.html">Sympa Mailing Lists Management Software</A>
<B> Previous:</B> <A NAME="tex2html670"
  HREF="node10.html">9. Mailing list definition</A>
 &nbsp <B>  <A NAME="tex2html678"
  HREF="node1.html">Contents</A></B> 
 &nbsp <B>  <A NAME="tex2html680"
  HREF="node17.html">Index</A></B> 
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>

<UL>
<LI><A NAME="tex2html683"
  HREF="node11.html#SECTION001110000000000000000">10.1 List creation</A>
<UL>
<LI><A NAME="tex2html684"
  HREF="node11.html#SECTION001111000000000000000">10.1.1 create_list scenario</A>
<LI><A NAME="tex2html685"
  HREF="node11.html#SECTION001112000000000000000">10.1.2 typical list profile</A>
<LI><A NAME="tex2html686"
  HREF="node11.html#SECTION001113000000000000000">10.1.3 creating list alias</A>
</UL>
<LI><A NAME="tex2html687"
  HREF="node11.html#SECTION001120000000000000000">10.2 List edition</A>
</UL>
<!--End of Table of Child-Links-->
<HR>

<H1><A NAME="SECTION001100000000000000000"></A>
    <A NAME="web-ml-creation"></A>
<BR>
10. Creating and editing mailing using the web
</H1>

<P>
The management of mailing lists by list owners will usually be
done via the web interface. This 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. Therefore, a complete
installation requires some careful planning, although default
values should be acceptable for most sites.

<P>
Some features are already available, others will be shortly, as specified
in the documentation.

<P>

<H1><A NAME="SECTION001110000000000000000">
10.1 List creation</A>
</H1>

<P>
Listmasters have all privileges. Currently the listmaster
is defined in <A NAME="4299"></A><TT>sympa.conf</TT> but in the future, it might be possible to
define one listmaster per virtual robot. 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 <A NAME="4302"></A><TT>create_list</TT> scenario.

<P>

<H2><A NAME="SECTION001111000000000000000">
10.1.1 create_list scenario</A>
</H2>

<P>
This scenario can apply any condition concerning the [sender]
(ie: WWSympa user), and it must return <A NAME="4305"></A><TT>reject</TT>, <A NAME="4308"></A><TT>do_it</TT>
or <A NAME="4311"></A><TT>listmaster</TT>.
Only in cases where a user is authorized by the create_list scenario
will the "create" button be available in the main menu.
If the scenario returns <A NAME="4314"></A><TT>do_it</TT>, 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 <A NAME="4317"></A><TT>pending</TT> 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.

<P>

<H2><A NAME="SECTION001112000000000000000">
10.1.2 typical list profile</A>
</H2>

<P>
Mailing lists can have many different uses. <I>Sympa</I> offers a
wide choice of parameters to adapt a list's behavior
to different situations. Users might have difficulty selecting all the
correct parameters, so instead the create list form asks
the list creator simply to choose a profile for the list, and to fill in
the owner's e-mail and the list subject together with a short description.

<P>
List profiles can be stored in <A NAME="4321"></A><TT>~sympa/etc/create_list_templates</TT> or
<A NAME="4326"></A><TT>~sympa/bin/etc/create_list_templates</TT>, which are part of the Sympa
distribution and should not be modified.  
<A NAME="4331"></A><TT>~sympa/etc/create_list_templates</TT>, which will not be
overwritten by make install, is intended to contain site customizations.

<P>
A list profile is an almost complete list configuration, but with a number of missing fields
(such as owner e-mail)
to be replaced by WWSympa at installation time. It is easy to create new list 
templates by modifying existing ones. Contributions to the distribution are welcome.

<P>
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
<A NAME="4336"></A><TT>~sympa/etc/create_list_templates</TT> and
<A NAME="4341"></A><TT>~sympa/bin/etc/create_list_templates</TT> directory, then the local profile 
will be used by WWSympa. 

<P>
Another way to control publicly available profiles is to
edit the <A NAME="4346"></A><TT>create_list.conf</TT> file (the default for this file is in
the <A NAME="4349"></A><TT>~sympa/bin/etc/</TT> directory, and you may create your own customized
version in <A NAME="4354"></A><TT>~sympa/etc/</TT>).
This file controls which of the available list templates are to be displayed. Example :<PRE>
# Do not allow the public_anonymous profile
public_anonymous hidden
* read
</PRE>

<P>
When a list is created, whatever its status (<A NAME="4359"></A><TT>pending</TT> or
<A NAME="4362"></A><TT>open</TT>), the owner can use WWSympa admin features to modify list
parameters (future version), or to edit the welcome message, and so on.

<P>
WWSympa logs the creation and all modifications to a list as part of the list's
<A NAME="4365"></A><TT>config</TT> file (and old configuration files are saved).

<P>

<H2><A NAME="SECTION001113000000000000000">
10.1.3 creating list alias</A>
</H2>

<P>
If you defined an alias_manager in <A NAME="4368"></A><TT>wwsympa.conf</TT> 
(see <A HREF="node6.html#alias-manager">5.3.1</A>, page&nbsp;<A HREF="node6.html#alias-manager"><IMG  ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>), <A NAME="4371"></A><I>WWSympa</I> 
will run this script for installing aliases. You can write your
own alias_manager script, adapted to your MTA or mail configuration,
provided that it recognizes the same set of parameters.

<P>

<H1><A NAME="SECTION001120000000000000000"></A>
<A NAME="list-edition"></A>
<BR>
10.2 List edition
</H1>

<P>
For each parameter, you may specify (via the <A NAME="4374"></A><TT>~sympa/etc/edit_list.conf</TT>
configuration file) who has the right to edit the parameter concerned ; the default 
<A NAME="4379"></A><TT>~sympa/bin/etc/edit_list.conf</TT> is reasonably safe.

<P><PRE>
     examples :

         \# only listmaster can edit user\_data\_source, priority, ...
         user\_data\_source listmaster  

         priority listmaster
      
         \# only privileged owner can modify  editor parameter, send, ...
         editor privileged\_owner

         send privileged\_owner

         \# other parameters can be changed by simple owners
         default owner
</PRE>

<P>
Privileged owners are defined in the list's <A NAME="4384"></A><TT>config</TT> file as follows :
	<PRE>
		owner
		email owners.email@foo.bar
      		profile privileged
</PRE>

<P>
The following rules are hard coded in WWSympa :

<UL>
<LI>listmaster is privileged owner of any list 

<P>
</LI>
<LI>only listmaster can edit the "profile privileged"
      owner attribute 

<P>
</LI>
<LI>owners can edit their own attributes (except profile and e-mail)

<P>
</LI>
<LI>the requestor creating a new list becomes privileged owner

<P>
</LI>
<LI>privileged owners can edit any gecos/reception/info attribute
of any owner

<P>
</LI>
<LI>privileged owners can edit owners' e-mail addresses (but not privileged owners' e-mail addresses)

<P>
</LI>
</UL>

<P>
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.

<P>

<HR>
<!--Navigation Panel-->
<A NAME="tex2html681"
  HREF="node12.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A> 
<A NAME="tex2html675"
  HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A> 
<A NAME="tex2html669"
  HREF="node10.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A> 
<A NAME="tex2html677"
  HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A> 
<A NAME="tex2html679"
  HREF="node17.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html682"
  HREF="node12.html">11. List configuration parameters</A>
<B> Up:</B> <A NAME="tex2html676"
  HREF="sympa.html">Sympa Mailing Lists Management Software</A>
<B> Previous:</B> <A NAME="tex2html670"
  HREF="node10.html">9. Mailing list definition</A>
 &nbsp <B>  <A NAME="tex2html678"
  HREF="node1.html">Contents</A></B> 
 &nbsp <B>  <A NAME="tex2html680"
  HREF="node17.html">Index</A></B> 
<!--End of Navigation Panel-->
<ADDRESS>
root
2001-06-05
</ADDRESS>
</BODY>
</HTML>