Commit 55c91557 authored by sympa-authors's avatar sympa-authors
Browse files

[G. Bouteille] New feature: 1st version of list families. List families make...

[G. Bouteille] New feature: 1st version of list families. List families make it possible to automatically create a set of mailing lists that share a common configuration template,
 a set of constraints, templates and authZ scenarios. Family instantiation requires an XML document that defines mailing lists.


git-svn-id: https://subversion.renater.fr/sympa/trunk@2606 05aa8bb8-cd2b-0410-b1d7-8918dfa770ce
parent 5c12b772
......@@ -9,9 +9,9 @@ original version by: Nikos Drakos, CBLU, University of Leeds
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Sympa Mailing Lists Management Software version 4.2b.4
<TITLE>Sympa Mailing Lists Management Software version 4.2b.5
</TITLE>
<META NAME="description" CONTENT="Sympa Mailing Lists Management Software version 4.2b.4
<META NAME="description" CONTENT="Sympa Mailing Lists Management Software version 4.2b.5
">
<META NAME="keywords" CONTENT="sympa">
<META NAME="resource-type" CONTENT="document">
......@@ -37,7 +37,7 @@ original version by: Nikos Drakos, CBLU, University of Leeds
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html111"
HREF="node23.html">
HREF="node24.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html114"
......@@ -45,7 +45,7 @@ original version by: Nikos Drakos, CBLU, University of Leeds
&nbsp <B> <A NAME="tex2html110"
HREF="node1.html">Contents</A></B>
&nbsp <B> <A NAME="tex2html112"
HREF="node23.html">Index</A></B>
HREF="node24.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
......@@ -58,13 +58,13 @@ of this documentation.
<H1 ALIGN="CENTER"><FONT SIZE="+4"><B>Sympa
<BR><FONT SIZE="+3"><B>Mailing Lists Management Software
<BR>
version 4.2b.4
version 4.2b.5
<BR></B></FONT></B></FONT></H1>
<P ALIGN="CENTER"><STRONG>Serge Aumont,
Olivier Sala&#252;n,
Christophe Wolfhugel,
</STRONG></P>
<P ALIGN="CENTER"><STRONG>12 October 2004</STRONG></P>
<P ALIGN="CENTER"><STRONG>20 October 2004</STRONG></P>
<P>
......@@ -321,92 +321,105 @@ version 4.2b.4
</UL>
<BR>
<LI><A NAME="tex2html217"
HREF="node15.html">14. Creating and editing mailing using the web</A>
HREF="node15.html">14. List creation, families and list edition</A>
<UL>
<LI><A NAME="tex2html218"
HREF="node15.html#SECTION001510000000000000000">14.1 List creation</A>
HREF="node15.html#SECTION001510000000000000000">14.1 List families</A>
<LI><A NAME="tex2html219"
HREF="node15.html#SECTION001520000000000000000">14.2 List edition</A>
HREF="node15.html#SECTION001520000000000000000">14.2 List creation on command line with <TT>sympa.pl</TT></A>
<LI><A NAME="tex2html220"
HREF="node15.html#SECTION001530000000000000000">14.3 Creating and editing mailing using the web</A>
</UL>
<BR>
<LI><A NAME="tex2html220"
HREF="node16.html">15. List configuration parameters</A>
<UL>
<LI><A NAME="tex2html221"
HREF="node16.html#SECTION001610000000000000000">15.1 List description</A>
HREF="node16.html">15. Lists Families</A>
<UL>
<LI><A NAME="tex2html222"
HREF="node16.html#SECTION001620000000000000000">15.2 Data source related</A>
HREF="node16.html#SECTION001610000000000000000">15.1 Family concept</A>
<LI><A NAME="tex2html223"
HREF="node16.html#SECTION001630000000000000000">15.3 Command related</A>
HREF="node16.html#SECTION001620000000000000000">15.2 Using family</A>
</UL>
<BR>
<LI><A NAME="tex2html224"
HREF="node16.html#SECTION001640000000000000000">15.4 List tuning</A>
HREF="node17.html">16. List configuration parameters</A>
<UL>
<LI><A NAME="tex2html225"
HREF="node16.html#SECTION001650000000000000000">15.5 Bounce related</A>
HREF="node17.html#SECTION001710000000000000000">16.1 List description</A>
<LI><A NAME="tex2html226"
HREF="node16.html#SECTION001660000000000000000">15.6 Archive related</A>
HREF="node17.html#SECTION001720000000000000000">16.2 Data source related</A>
<LI><A NAME="tex2html227"
HREF="node16.html#SECTION001670000000000000000">15.7 Spam protection</A>
</UL>
<BR>
HREF="node17.html#SECTION001730000000000000000">16.3 Command related</A>
<LI><A NAME="tex2html228"
HREF="node17.html">16. Shared documents</A>
<UL>
HREF="node17.html#SECTION001740000000000000000">16.4 List tuning</A>
<LI><A NAME="tex2html229"
HREF="node17.html#SECTION001710000000000000000">16.1 The three kind of operations on a document</A>
HREF="node17.html#SECTION001750000000000000000">16.5 Bounce related</A>
<LI><A NAME="tex2html230"
HREF="node17.html#SECTION001720000000000000000">16.2 The description file</A>
HREF="node17.html#SECTION001760000000000000000">16.6 Archive related</A>
<LI><A NAME="tex2html231"
HREF="node17.html#SECTION001730000000000000000">16.3 The predefined authorization scenarios</A>
HREF="node17.html#SECTION001770000000000000000">16.7 Spam protection</A>
<LI><A NAME="tex2html232"
HREF="node17.html#SECTION001740000000000000000">16.4 Access control</A>
<LI><A NAME="tex2html233"
HREF="node17.html#SECTION001750000000000000000">16.5 Shared document actions</A>
<LI><A NAME="tex2html234"
HREF="node17.html#SECTION001760000000000000000">16.6 Template files</A>
HREF="node17.html#SECTION001780000000000000000">16.8 Intern parameters</A>
</UL>
<BR>
<LI><A NAME="tex2html233"
HREF="node18.html">17. Shared documents</A>
<UL>
<LI><A NAME="tex2html234"
HREF="node18.html#SECTION001810000000000000000">17.1 The three kind of operations on a document</A>
<LI><A NAME="tex2html235"
HREF="node18.html">17. Bounce management</A>
HREF="node18.html#SECTION001820000000000000000">17.2 The description file</A>
<LI><A NAME="tex2html236"
HREF="node19.html">18. Antivirus</A>
HREF="node18.html#SECTION001830000000000000000">17.3 The predefined authorization scenarios</A>
<LI><A NAME="tex2html237"
HREF="node20.html">19. Using <I>Sympa</I> with LDAP</A>
HREF="node18.html#SECTION001840000000000000000">17.4 Access control</A>
<LI><A NAME="tex2html238"
HREF="node21.html">20. <I>Sympa</I> with S/MIME and HTTPS</A>
<UL>
HREF="node18.html#SECTION001850000000000000000">17.5 Shared document actions</A>
<LI><A NAME="tex2html239"
HREF="node21.html#SECTION002110000000000000000">20.1 Signed message distribution</A>
HREF="node18.html#SECTION001860000000000000000">17.6 Template files</A>
</UL>
<BR>
<LI><A NAME="tex2html240"
HREF="node21.html#SECTION002120000000000000000">20.2 Use of S/MIME signature by Sympa itself</A>
HREF="node19.html">18. Bounce management</A>
<LI><A NAME="tex2html241"
HREF="node21.html#SECTION002130000000000000000">20.3 Use of S/MIME encryption</A>
HREF="node20.html">19. Antivirus</A>
<LI><A NAME="tex2html242"
HREF="node21.html#SECTION002140000000000000000">20.4 S/Sympa configuration</A>
HREF="node21.html">20. Using <I>Sympa</I> with LDAP</A>
<LI><A NAME="tex2html243"
HREF="node21.html#SECTION002150000000000000000">20.5 Managing certificates with tasks</A>
</UL>
<BR>
<LI><A NAME="tex2html244"
HREF="node22.html">21. Using <I>Sympa</I> commands</A>
HREF="node22.html">21. <I>Sympa</I> with S/MIME and HTTPS</A>
<UL>
<LI><A NAME="tex2html244"
HREF="node22.html#SECTION002210000000000000000">21.1 Signed message distribution</A>
<LI><A NAME="tex2html245"
HREF="node22.html#SECTION002210000000000000000">21.1 User commands</A>
HREF="node22.html#SECTION002220000000000000000">21.2 Use of S/MIME signature by Sympa itself</A>
<LI><A NAME="tex2html246"
HREF="node22.html#SECTION002220000000000000000">21.2 Owner commands</A>
HREF="node22.html#SECTION002230000000000000000">21.3 Use of S/MIME encryption</A>
<LI><A NAME="tex2html247"
HREF="node22.html#SECTION002230000000000000000">21.3 Moderator commands</A>
HREF="node22.html#SECTION002240000000000000000">21.4 S/Sympa configuration</A>
<LI><A NAME="tex2html248"
HREF="node22.html#SECTION002250000000000000000">21.5 Managing certificates with tasks</A>
</UL>
<BR>
<LI><A NAME="tex2html248"
HREF="node23.html">Index</A>
<LI><A NAME="tex2html249"
HREF="node24.html">About this document ...</A>
HREF="node23.html">22. Using <I>Sympa</I> commands</A>
<UL>
<LI><A NAME="tex2html250"
HREF="node23.html#SECTION002310000000000000000">22.1 User commands</A>
<LI><A NAME="tex2html251"
HREF="node23.html#SECTION002320000000000000000">22.2 Owner commands</A>
<LI><A NAME="tex2html252"
HREF="node23.html#SECTION002330000000000000000">22.3 Moderator commands</A>
</UL>
<BR>
<LI><A NAME="tex2html253"
HREF="node24.html">Index</A>
<LI><A NAME="tex2html254"
HREF="node25.html">About this document ...</A>
</UL>
<!--End of Table of Child-Links-->
<BR><HR>
<ADDRESS>
root
2004-10-12
2004-10-20
</ADDRESS>
</BODY>
</HTML>
This diff is collapsed.
This diff is collapsed.
......@@ -29,32 +29,32 @@ original version by: Nikos Drakos, CBLU, University of Leeds
<BODY TEXT="#000000" BGCOLOR="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html939"
<A NAME="tex2html961"
HREF="node12.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html933"
<A NAME="tex2html955"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html927"
<A NAME="tex2html949"
HREF="node10.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html935"
<A NAME="tex2html957"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html937"
HREF="node23.html">
<A NAME="tex2html959"
HREF="node24.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html940"
<B> Next:</B> <A NAME="tex2html962"
HREF="node12.html">11. Virtual robot</A>
<B> Up:</B> <A NAME="tex2html934"
<B> Up:</B> <A NAME="tex2html956"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html928"
<B> Previous:</B> <A NAME="tex2html950"
HREF="node10.html">9. Authentication</A>
&nbsp <B> <A NAME="tex2html936"
&nbsp <B> <A NAME="tex2html958"
HREF="node1.html">Contents</A></B>
&nbsp <B> <A NAME="tex2html938"
HREF="node23.html">Index</A></B>
&nbsp <B> <A NAME="tex2html960"
HREF="node24.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
......@@ -62,38 +62,38 @@ original version by: Nikos Drakos, CBLU, University of Leeds
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html941"
<LI><A NAME="tex2html963"
HREF="node11.html#SECTION001110000000000000000">10.1 rules specifications</A>
<LI><A NAME="tex2html942"
<LI><A NAME="tex2html964"
HREF="node11.html#SECTION001120000000000000000">10.2 LDAP Named Filters</A>
<UL>
<LI><A NAME="tex2html943"
<LI><A NAME="tex2html965"
HREF="node11.html#SECTION001121000000000000000">10.2.1 Definition</A>
<LI><A NAME="tex2html944"
<LI><A NAME="tex2html966"
HREF="node11.html#SECTION001122000000000000000">10.2.2 Search Condition</A>
</UL>
<BR>
<LI><A NAME="tex2html945"
<LI><A NAME="tex2html967"
HREF="node11.html#SECTION001130000000000000000">10.3 scenario inclusion</A>
<LI><A NAME="tex2html946"
<LI><A NAME="tex2html968"
HREF="node11.html#SECTION001140000000000000000">10.4 Hidding scenario files</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION001100000000000000000"></A>
<A NAME="scenarios"></A><A NAME="1603"></A>
<A NAME="scenarios"></A><A NAME="1617"></A>
<BR>
10. Authorization scenarios
</H1>
<P>
List parameters controlling the behavior of commands are linked to different authorization scenarios.
For example : the <A NAME="6321"></A><TT>send private</TT> parameter is related to the send.private scenario.
For example : the <A NAME="6571"></A><TT>send private</TT> parameter is related to the send.private scenario.
There are four possible locations for a authorization scenario. When <I>Sympa</I> seeks to apply an authorization scenario, it
looks first in the related list directory <A NAME="6337"></A><TT>/home/sympa/expl/<TT>&lt;</TT>list<TT>&gt;</TT>/scenari</TT>. If it
does not find the file there, it scans the current robot configuration directory <A NAME="6346"></A><TT>/home/sympa/etc/my.domain.org/scenari</TT>, then the site's configuration directory <A NAME="6349"></A><TT>/home/sympa/etc/scenari</TT>,
and finally <A NAME="6352"></A><TT>/home/sympa/bin/etc/scenari</TT>, which is the directory installed by the Makefile.
looks first in the related list directory <A NAME="6587"></A><TT>/home/sympa/expl/<TT>&lt;</TT>list<TT>&gt;</TT>/scenari</TT>. If it
does not find the file there, it scans the current robot configuration directory <A NAME="6596"></A><TT>/home/sympa/etc/my.domain.org/scenari</TT>, then the site's configuration directory <A NAME="6599"></A><TT>/home/sympa/etc/scenari</TT>,
and finally <A NAME="6602"></A><TT>/home/sympa/bin/etc/scenari</TT>, which is the directory installed by the Makefile.
<P>
An authorization scenario is a small configuration language to describe who
......@@ -120,12 +120,12 @@ Each authorization scenario rule contains :
SRC="img2.png"
ALT="$]$"> for the listname etc.
</LI>
<LI>an authentication method. The authentication method can be <A NAME="6356"></A><TT>smtp</TT>,
<A NAME="6359"></A><TT>md5</TT> or <A NAME="6362"></A><TT>smime</TT>. The rule is applied by <I>Sympa</I> if both condition
and authentication method match the runtime context. <A NAME="6366"></A><TT>smtp</TT> is used if
<I>Sympa</I> use the SMTP <A NAME="6370"></A><TT>from:</TT> header , <A NAME="6373"></A><TT>md5</TT> is used if a unique
md5 key as been returned by the requestor to validate her message, <A NAME="6376"></A><TT>smime</TT>
is used for signed messages (see <A HREF="node21.html#smimeforsign">20.4.3</A>, page&nbsp;<A HREF="node21.html#smimeforsign"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
<LI>an authentication method. The authentication method can be <A NAME="6606"></A><TT>smtp</TT>,
<A NAME="6609"></A><TT>md5</TT> or <A NAME="6612"></A><TT>smime</TT>. The rule is applied by <I>Sympa</I> if both condition
and authentication method match the runtime context. <A NAME="6616"></A><TT>smtp</TT> is used if
<I>Sympa</I> use the SMTP <A NAME="6620"></A><TT>from:</TT> header , <A NAME="6623"></A><TT>md5</TT> is used if a unique
md5 key as been returned by the requestor to validate her message, <A NAME="6626"></A><TT>smime</TT>
is used for signed messages (see <A HREF="node22.html#smimeforsign">21.4.3</A>, page&nbsp;<A HREF="node22.html#smimeforsign"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
</LI>
<LI>a returned atomic action that will be executed by <I>Sympa</I> if the rule matches
......@@ -248,19 +248,19 @@ probably create authorization scenarios for your own need. In this case, don't f
and wwsympa because authorization scenarios are not reloaded dynamicaly.
<P>
These standard authorization scenarios are located in the <A NAME="6382"></A><TT>/home/sympa/bin/etc/scenari/</TT>
These standard authorization scenarios are located in the <A NAME="6632"></A><TT>/home/sympa/bin/etc/scenari/</TT>
directory. Default scenarios are named <TT>&lt;</TT>command<TT>&gt;</TT>.default.
<P>
You may also define and name your own authorization scenarios. Store them in the
<A NAME="6385"></A><TT>/home/sympa/etc/scenari</TT> directory. They will not be overwritten by Sympa release.
Scenarios can also be defined for a particular virtual robot (using directory <A NAME="6400"></A><TT>/home/sympa/etc/<TT>&lt;</TT>robot<TT>&gt;</TT>/scenari</TT>) or for a list ( <A NAME="6427"></A><TT>/home/sympa/expl/<TT>&lt;</TT>robot<TT>&gt;</TT>/<TT>&lt;</TT>list<TT>&gt;</TT>/scenari</TT> ).
<A NAME="6635"></A><TT>/home/sympa/etc/scenari</TT> directory. They will not be overwritten by Sympa release.
Scenarios can also be defined for a particular virtual robot (using directory <A NAME="6650"></A><TT>/home/sympa/etc/<TT>&lt;</TT>robot<TT>&gt;</TT>/scenari</TT>) or for a list ( <A NAME="6677"></A><TT>/home/sympa/expl/<TT>&lt;</TT>robot<TT>&gt;</TT>/<TT>&lt;</TT>list<TT>&gt;</TT>/scenari</TT> ).
<P>
Example:
<P>
Copy the previous scenario to <A NAME="6442"></A><TT>scenari/subscribe.rennes1</TT> :
Copy the previous scenario to <A NAME="6692"></A><TT>scenari/subscribe.rennes1</TT> :
<P><PRE>
equal([sender], 'userxxx@univ-rennes1.fr') smtp,smime -&gt; reject
......@@ -287,7 +287,7 @@ subscribe rennes1
At the moment Named Filters are only used in authorization scenarios. They enable to select a category of people who will be authorized or not to realise some actions.
<P>
As a consequence, you can grant privileges in a list to people belonging to an <A NAME="6445"></A>LDAP directory thanks to an authorization scenario.
As a consequence, you can grant privileges in a list to people belonging to an <A NAME="6695"></A>LDAP directory thanks to an authorization scenario.
<P>
......@@ -296,7 +296,7 @@ As a consequence, you can grant privileges in a list to people belonging to an <
</H2>
<P>
People are selected through an <A NAME="6446"></A>LDAP filter defined in a configuration file. This file must have the extension '.ldap'.It is stored in <A NAME="6447"></A><TT>/home/sympa/etc/search_filters/</TT>.
People are selected through an <A NAME="6696"></A>LDAP filter defined in a configuration file. This file must have the extension '.ldap'.It is stored in <A NAME="6697"></A><TT>/home/sympa/etc/search_filters/</TT>.
<P>
You must give several informations in order to create a Named Filter:
......@@ -450,36 +450,36 @@ at the my.domain.orgrobot level only.
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html939"
<A NAME="tex2html961"
HREF="node12.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html933"
<A NAME="tex2html955"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html927"
<A NAME="tex2html949"
HREF="node10.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html935"
<A NAME="tex2html957"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html937"
HREF="node23.html">
<A NAME="tex2html959"
HREF="node24.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html940"
<B> Next:</B> <A NAME="tex2html962"
HREF="node12.html">11. Virtual robot</A>
<B> Up:</B> <A NAME="tex2html934"
<B> Up:</B> <A NAME="tex2html956"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html928"
<B> Previous:</B> <A NAME="tex2html950"
HREF="node10.html">9. Authentication</A>
&nbsp <B> <A NAME="tex2html936"
&nbsp <B> <A NAME="tex2html958"
HREF="node1.html">Contents</A></B>
&nbsp <B> <A NAME="tex2html938"
HREF="node23.html">Index</A></B>
&nbsp <B> <A NAME="tex2html960"
HREF="node24.html">Index</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
root
2004-10-12
2004-10-20
</ADDRESS>
</BODY>
</HTML>
......@@ -29,32 +29,32 @@ original version by: Nikos Drakos, CBLU, University of Leeds
<BODY TEXT="#000000" BGCOLOR="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html959"
<A NAME="tex2html981"
HREF="node13.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html953"
<A NAME="tex2html975"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html947"
<A NAME="tex2html969"
HREF="node11.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html955"
<A NAME="tex2html977"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html957"
HREF="node23.html">
<A NAME="tex2html979"
HREF="node24.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html960"
<B> Next:</B> <A NAME="tex2html982"
HREF="node13.html">12. Customizing Sympa/WWSympa</A>
<B> Up:</B> <A NAME="tex2html954"
<B> Up:</B> <A NAME="tex2html976"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html948"
<B> Previous:</B> <A NAME="tex2html970"
HREF="node11.html">10. Authorization scenarios</A>
&nbsp <B> <A NAME="tex2html956"
&nbsp <B> <A NAME="tex2html978"
HREF="node1.html">Contents</A></B>
&nbsp <B> <A NAME="tex2html958"
HREF="node23.html">Index</A></B>
&nbsp <B> <A NAME="tex2html980"
HREF="node24.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
......@@ -62,16 +62,16 @@ original version by: Nikos Drakos, CBLU, University of Leeds
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html961"
<LI><A NAME="tex2html983"
HREF="node12.html#SECTION001210000000000000000">11.1 How to create a virtual robot</A>
<LI><A NAME="tex2html962"
<LI><A NAME="tex2html984"
HREF="node12.html#SECTION001220000000000000000">11.2 robot.conf</A>
<UL>
<LI><A NAME="tex2html963"
<LI><A NAME="tex2html985"
HREF="node12.html#SECTION001221000000000000000">11.2.1 Robot customization</A>
</UL>
<BR>
<LI><A NAME="tex2html964"
<LI><A NAME="tex2html986"
HREF="node12.html#SECTION001230000000000000000">11.3 Managing multiple virtual robots</A>
</UL>
<!--End of Table of Child-Links-->
......@@ -111,7 +111,7 @@ Note that the main limitation of virtual robots in Sympa is that you cannot crea
</H1>
<P>
You don't need to install several Sympa servers. A single <A NAME="6454"></A><TT>sympa.pl</TT> daemon
You don't need to install several Sympa servers. A single <A NAME="6704"></A><TT>sympa.pl</TT> daemon
and one or more fastcgi servers can serve all virtual robot. Just configure the
server environment in order to accept the new domain definition.
......@@ -155,7 +155,7 @@ FastCgiServer /home/sympa/bin/wwsympa.fcgi -processes 3 -idle-timeout 120
<P>
</LI>
<LI>Create a <A NAME="6457"></A><TT>robot.conf</TT> for the virtual robot (current web interface does
<LI>Create a <A NAME="6707"></A><TT>robot.conf</TT> for the virtual robot (current web interface does
not provide Virtual robot creation yet).
<P>
......@@ -168,15 +168,15 @@ not provide Virtual robot creation yet).
11.2 robot.conf</A>
</H1>
A robot is named by its domain, let's say my.domain.organd defined by a directory
<A NAME="6460"></A><TT>/home/sympa/etc/my.domain.org</TT>. This directory must contain at least a
<A NAME="6463"></A><TT>robot.conf</TT> file. This files has the same format as <A NAME="6466"></A><TT>/etc/sympa.conf</TT>
<A NAME="6710"></A><TT>/home/sympa/etc/my.domain.org</TT>. This directory must contain at least a
<A NAME="6713"></A><TT>robot.conf</TT> file. This files has the same format as <A NAME="6716"></A><TT>/etc/sympa.conf</TT>
(have a look at robot.conf in the sample dir).
Only the following parameters can be redefined for a particular robot :
<P>
<UL>
<LI><A NAME="6469"></A><TT>http_host</TT>
<LI><A NAME="6719"></A><TT>http_host</TT>
<BR>
This hostname will be compared with 'SERVER_NAME' environment variable in wwsympa.fcgi
to determine the current Virtual Robot. You can a path at the end of this parameter if
......@@ -188,65 +188,65 @@ This hostname will be compared with 'SERVER_NAME' environment variable in wwsymp
<P>
</LI>
<LI><A NAME="6472"></A><TT>wwsympa_url</TT>
<LI><A NAME="6722"></A><TT>wwsympa_url</TT>
<BR>
The base URL of WWSympa
<P>
</LI>
<LI><A NAME="6475"></A><TT>soap_url</TT>
<LI><A NAME="6725"></A><TT>soap_url</TT>
<BR>
The base URL of Sympa's SOAP server (if it is running ; see&nbsp;<A HREF="node9.html#soap">8</A>, page&nbsp;<A HREF="node9.html#soap"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>)
<P>
</LI>
<LI><A NAME="6478"></A><TT>cookie_domain</TT>
<LI><A NAME="6728"></A><TT>cookie_domain</TT>
<P>
</LI>
<LI><A NAME="6481"></A><TT>email</TT>
<LI><A NAME="6731"></A><TT>email</TT>
<P>
</LI>
<LI><A NAME="6484"></A><TT>title</TT>
<LI><A NAME="6734"></A><TT>title</TT>
<P>
</LI>
<LI><A NAME="6487"></A><TT>default_home</TT>
<LI><A NAME="6737"></A><TT>default_home</TT>
<P>
</LI>
<LI><A NAME="6490"></A><TT>create_list</TT>
<LI><A NAME="6740"></A><TT>create_list</TT>
<P>
</LI>
<LI><A NAME="6493"></A><TT>lang</TT>
<LI><A NAME="6743"></A><TT>lang</TT>
<P>
</LI>
<LI><A NAME="6496"></A><TT>supported_lang</TT>
<LI><A NAME="6746"></A><TT>supported_lang</TT>
<P>
</LI>
<LI><A NAME="6499"></A><TT>log_smtp</TT>
<LI><A NAME="6749"></A><TT>log_smtp</TT>
<P>
</LI>
<LI><A NAME="6502"></A><TT>listmaster</TT>
<LI><A NAME="6752"></A><TT>listmaster</TT>
<P>
</LI>
<LI><A NAME="6505"></A><TT>max_size</TT>
<LI><A NAME="6755"></A><TT>max_size</TT>
<P>
</LI>
<LI><A NAME="6508"></A><TT>dark_color</TT>, <A NAME="6511"></A><TT>light_color</TT>, <A NAME="6514"></A><TT>text_color</TT>, <A NAME="6517"></A><TT>bg_color</TT>, <A NAME="6520"></A><TT>error_color</TT>, <A NAME="6523"></A><TT>selected_color</TT>, <A NAME="6526"></A><TT>shaded_color</TT>
<LI><A NAME="6758"></A><TT>dark_color</TT>, <A NAME="6761"></A><TT>light_color</TT>, <A NAME="6764"></A><TT>text_color</TT>, <A NAME="6767"></A><TT>bg_color</TT>, <A NAME="6770"></A><TT>error_color</TT>, <A NAME="6773"></A><TT>selected_color</TT>, <A NAME="6776"></A><TT>shaded_color</TT>
</LI>
</UL>
<P>
These settings overwrite the equivalent global parameter defined in <A NAME="6529"></A><TT>/etc/sympa.conf</TT>
for my.domain.orgrobot ; the main <A NAME="6532"></A><TT>listmaster</TT> still has privileges on Virtual
These settings overwrite the equivalent global parameter defined in <A NAME="6779"></A><TT>/etc/sympa.conf</TT>
for my.domain.orgrobot ; the main <A NAME="6782"></A><TT>listmaster</TT> still has privileges on Virtual
Robots though. The http_host parameter is compared by wwsympa with the SERVER_NAME
environment variable to recognize which robot is in used.
......@@ -260,10 +260,10 @@ environment variable to recognize which robot is in used.
If needed, you can customize each virtual robot using its set of templates and authorization scenarios.
<P>
<A NAME="6535"></A><TT>/home/sympa/etc/my.domain.org/wws_templates/</TT>,
<A NAME="6538"></A><TT>/home/sympa/etc/my.domain.org/templates/</TT>,
<A NAME="6541"></A><TT>/home/sympa/etc/my.domain.org/scenari/</TT> directories are searched when
loading templates or scenari before searching into <A NAME="6544"></A><TT>/home/sympa/etc</TT> and <A NAME="6547"></A><TT>/home/sympa/bin/etc</TT>. This allows to define different privileges and a different GUI for a Virtual Robot.
<A NAME="6785"></A><TT>/home/sympa/etc/my.domain.org/wws_templates/</TT>,
<A NAME="6788"></A><TT>/home/sympa/etc/my.domain.org/templates/</TT>,
<A NAME="6791"></A><TT>/home/sympa/etc/my.domain.org/scenari/</TT> directories are searched when
loading templates or scenari before searching into <A NAME="6794"></A><TT>/home/sympa/etc</TT> and <A NAME="6797"></A><TT>/home/sympa/bin/etc</TT>. This allows to define different privileges and a different GUI for a Virtual Robot.
<P>
......@@ -273,49 +273,49 @@ loading templates or scenari before searching into <A NAME="6544"></A><TT>/home/
<P>
If you are managing more than 2 virtual robots, then you might cinsider moving all the mailing lists in the default
robot to a dedicated virtual robot located in the <A NAME="6550"></A><TT>/home/sympa/expl/my.domain.org/</TT> directory. The main benefit of
robot to a dedicated virtual robot located in the <A NAME="6800"></A><TT>/home/sympa/expl/my.domain.org/</TT> directory. The main benefit of
this organisation is the ability to define default configuration elements (templates or authorization scenarios)
for this robot without inheriting them within other virtual robots.
<P>
To create such a virtual robot, you need to create <A NAME="6553"></A><TT>/home/sympa/expl/my.domain.org/</TT> and <A NAME="6556"></A><TT>/home/sympa/etc/my.domain.org/</TT> directories ;
customize <A NAME="6559"></A><TT>host</TT>, <A NAME="6562"></A><TT>http_host</TT> and <A NAME="6565"></A><TT>wwsympa_url</TT> parameters in the <A NAME="6568"></A><TT>/home/sympa/etc/my.domain.org/robot.conf</TT>