File: node8.html

package info (click to toggle)
sympa 4.1.5-2
links: PTS
area: main
in suites: sarge
size: 11,504 kB
ctags: 2,195
sloc: perl: 18,884; sh: 4,032; makefile: 1,173; ansic: 226; php: 105; lisp: 32
file content (664 lines) | stat: -rw-r--r-- 22,078 bytes
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<!--Converted with jLaTeX2HTML 2002 (1.62) JA patch-1.4
patched version by:  Kenshi Muto, Debian Project.
LaTeX2HTML 2002 (1.62),
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>7. WWSympa, Sympa's web interface</TITLE>
<META NAME="description" CONTENT="7. WWSympa, Sympa's web interface">
<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="jLaTeX2HTML v2002 JA patch-1.4">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

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

<LINK REL="next" HREF="node9.html">
<LINK REL="previous" HREF="node7.html">
<LINK REL="up" HREF="sympa.html">
<LINK REL="next" HREF="node9.html">
</HEAD>

<BODY TEXT="#000000" BGCOLOR="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html847"
  HREF="node9.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A> 
<A NAME="tex2html841"
  HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A> 
<A NAME="tex2html835"
  HREF="node7.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A> 
<A NAME="tex2html843"
  HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A> 
<A NAME="tex2html845"
  HREF="node23.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html848"
  HREF="node9.html">8. Sympa SOAP server</A>
<B> Up:</B> <A NAME="tex2html842"
  HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html836"
  HREF="node7.html">6. Sympa and its database</A>
 &nbsp <B>  <A NAME="tex2html844"
  HREF="node1.html">Contents</A></B> 
 &nbsp <B>  <A NAME="tex2html846"
  HREF="node23.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="tex2html849"
  HREF="node8.html#SECTION00810000000000000000">7.1 Organization</A>
<LI><A NAME="tex2html850"
  HREF="node8.html#SECTION00820000000000000000">7.2 Web server setup</A>
<UL>
<LI><A NAME="tex2html851"
  HREF="node8.html#SECTION00821000000000000000">7.2.1 wwsympa.fcgi access permissions</A>
<LI><A NAME="tex2html852"
  HREF="node8.html#SECTION00822000000000000000">7.2.2 Installing wwsympa.fcgi in your Apache server</A>
<LI><A NAME="tex2html853"
  HREF="node8.html#SECTION00823000000000000000">7.2.3 Using FastCGI</A>
</UL>
<BR>
<LI><A NAME="tex2html854"
  HREF="node8.html#SECTION00830000000000000000">7.3 wwsympa.conf parameters</A>
<UL>
<LI><A NAME="tex2html855"
  HREF="node8.html#SECTION00831000000000000000">7.3.1 arc_path</A>
<LI><A NAME="tex2html856"
  HREF="node8.html#SECTION00832000000000000000">7.3.2 archive_default_index thrd | mail</A>
<LI><A NAME="tex2html857"
  HREF="node8.html#SECTION00833000000000000000">7.3.3 archived_pidfile</A>
<LI><A NAME="tex2html858"
  HREF="node8.html#SECTION00834000000000000000">7.3.4 bounce_path</A>
<LI><A NAME="tex2html859"
  HREF="node8.html#SECTION00835000000000000000">7.3.5 bounced_pidfile</A>
<LI><A NAME="tex2html860"
  HREF="node8.html#SECTION00836000000000000000">7.3.6 cookie_expire</A>
<LI><A NAME="tex2html861"
  HREF="node8.html#SECTION00837000000000000000">7.3.7 cookie_domain</A>
<LI><A NAME="tex2html862"
  HREF="node8.html#SECTION00838000000000000000">7.3.8 default_home</A>
<LI><A NAME="tex2html863"
  HREF="node8.html#SECTION00839000000000000000">7.3.9 icons_url</A>
<LI><A NAME="tex2html864"
  HREF="node8.html#SECTION008310000000000000000">7.3.10 log_facility</A>
<LI><A NAME="tex2html865"
  HREF="node8.html#SECTION008311000000000000000">7.3.11 mhonarc</A>
<LI><A NAME="tex2html866"
  HREF="node8.html#SECTION008312000000000000000">7.3.12 htmlarea_url</A>
<LI><A NAME="tex2html867"
  HREF="node8.html#SECTION008313000000000000000">7.3.13 password_case sensitive | insensitive</A>
<LI><A NAME="tex2html868"
  HREF="node8.html#SECTION008314000000000000000">7.3.14 title</A>
<LI><A NAME="tex2html869"
  HREF="node8.html#SECTION008315000000000000000">7.3.15 use_fast_cgi   0 | 1</A>
</UL>
<BR>
<LI><A NAME="tex2html870"
  HREF="node8.html#SECTION00840000000000000000">7.4 MhOnArc</A>
<LI><A NAME="tex2html871"
  HREF="node8.html#SECTION00850000000000000000">7.5 Archiving daemon</A>
<LI><A NAME="tex2html872"
  HREF="node8.html#SECTION00860000000000000000">7.6 Database configuration</A>
</UL>
<!--End of Table of Child-Links-->
<HR>

<H1><A NAME="SECTION00800000000000000000">
7. WWSympa, Sympa's web interface</A>
</H1>

<P>
WWSympa is <I>Sympa</I>'s web interface.

<P>

<H1><A NAME="SECTION00810000000000000000"></A>
<A NAME="WWSympa"></A>
<BR>
7.1 Organization
</H1>

<P>
<A NAME="5864"></A><I>WWSympa</I> is fully integrated with <I>Sympa</I>. It uses <A NAME="5868"></A><TT>sympa.conf</TT>
and <I>Sympa</I>'s libraries. The default <I>Sympa</I> installation will also
install WWSympa.

<P>
Every single piece of HTML in <A NAME="5873"></A><I>WWSympa</I> is generated by the CGI code
using template files (See <A HREF="node13.html#tpl-format">12.1</A>, page&nbsp;<A HREF="node13.html#tpl-format"><IMG  ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
This facilitates internationalization of pages, as well as per-site
customization. 

<P>
The code consists of one single PERL CGI script, <A NAME="5876"></A><TT>WWSympa.fcgi</TT>.
To enhance performance you can configure <A NAME="5879"></A><I>WWSympa</I> to use
FastCGI ; the CGI will be persistent in memory.
<BR>
All data will be accessed through the CGI, including web archives.
This is required to allow the authentication scheme to be applied
systematically.

<P>
Authentication is based on passwords stored in the database table
user_table ; if the appropriate <A NAME="5882"></A><TT>Crypt::CipherSaber</TT> is
installed, password are encrypted in the database using reversible
encryption based on RC4. Otherwise they are stored in clear text.
In both cases reminding of passwords is possible.
 To keep track of authentication information <A NAME="5885"></A><I>WWSympa</I> 
uses HTTP cookies stored on the client side. The HTTP cookie only 
indicates that a specified e-mail address has been authenticated ;
permissions are evaluated when an action is requested.

<P>
The same web interface is used by the listmaster, list owners, subscribers and
others. Depending on permissions, the same URL may generate a different view.

<P>
<A NAME="5888"></A><I>WWSympa</I>'s main loop algorithm is roughly the following : 

<OL>
<LI>Check authentication information returned by 
	the HTTP cookie

<P>
</LI>
<LI>Evaluate user's permissions for the
        requested action 

<P>
</LI>
<LI>Process the requested action 

<P>
</LI>
<LI>Set up variables resulting from the action 

<P>
</LI>
<LI>Parse the HTML template files
</LI>
</OL>

<P>

<H1><A NAME="SECTION00820000000000000000">
7.2 Web server setup</A>
</H1>

<P>

<H2><A NAME="SECTION00821000000000000000">
7.2.1 wwsympa.fcgi access permissions</A>
</H2>

<P>
Because Sympa and WWSympa share a lot of files, <A NAME="5891"></A><TT>wwsympa.fcgi</TT>,
     must run with the same 
     uid/gid as <A NAME="5894"></A><TT>archived.pl</TT>, <A NAME="5897"></A><TT>bounced.pl</TT> and <A NAME="5900"></A><TT>sympa.pl</TT>.
     There are different ways to organize this :

<UL>
<LI>With some operating systems no special setup is required because
      wwsympa.fcgi is installed with suid and sgid bits, but this will not work
      if suid scripts are refused by your system.

<P>
</LI>
<LI>Run a dedicated Apache server with sympa.sympa as uid.gid (The Apache default
      is nobody.nobody)

<P>
</LI>
<LI>Use a Apache virtual host with sympa.sympa as uid.gid ; Apache
      needs to be compiled with suexec. Be aware that the Apache suexec usually define a lowest
      UID/GID allowed to be a target user for suEXEC. For most systems including binaries
      distribution of Apache, the default value 100 is common.
      So Sympa UID (and Sympa GID) must be higher then 100 or suexec must be tuned in order to allow
      lower UID/GID. Check http://httpd.apache.org/docs/suexec.html#install for details

<P>
The User and Group directive have to be set before the FastCgiServer directive
      is encountered.

<P>
</LI>
<LI>Otherwise, you can overcome restrictions on the execution of suid scripts
      by using a short C program, owned by sympa and with the suid bit set, to start
      <A NAME="5903"></A><TT>wwsympa.fcgi</TT>. Here is an example (with no guarantee attached) :<PRE>
#include &lt;unistd.h&gt;

#define WWSYMPA "/home/sympa/bin/wwsympa.fcgi"

int main(int argn, char **argv, char **envp) {
    argv[0] = WWSYMPA;
    execve(WWSYMPA,argv,envp);
}
</PRE>
</LI>
</UL>

<P>

<H2><A NAME="SECTION00822000000000000000">
7.2.2 Installing wwsympa.fcgi in your Apache server</A>
</H2>
     If you chose to run <A NAME="5906"></A><TT>wwsympa.fcgi</TT> as a simple CGI, you simply need to
     script alias it. 

<P><PRE>
     Example :
       	ScriptAlias /wws /home/sympa/bin/wwsympa.fcgi
</PRE>

<P>
Running  FastCGI will provide much faster responses from your server and 
     reduce load (to understand why, read 
     <A NAME="tex2html20"
  HREF="http://www.fastcgi.com/fcgi-devkit-2.1/doc/fcgi-perf.htm">http://www.fastcgi.com/fcgi-devkit-2.1/doc/fcgi-perf.htm</A>)

<P><PRE>
     Example :
	FastCgiServer /home/sympa/bin/wwsympa.fcgi -processes 2
	&lt;Location /wws&gt;
   	  SetHandler fastcgi-script
	&lt;/Location&gt;

	ScriptAlias /wws /home/sympa/bin/wwsympa.fcgi
</PRE>

<P>
If you run Virtual robots, then the FastCgiServer(s) can serve multiple robots. 
Therefore you need to define it in the common section of your Apache configuration
file.

<P>

<H2><A NAME="SECTION00823000000000000000">
7.2.3 Using FastCGI</A>
</H2>

<P>
<A NAME="tex2html21"
  HREF="http://www.fastcgi.com/">FastCGI</A>
is an extention to CGI that provides persistency for CGI programs. It is extemely useful
with <A NAME="5909"></A><I>WWSympa</I> since source code interpretation and all initialisation tasks are performed only once, at server startup ; then
file wwsympa.fcgi instances are waiting for clients requests. 

<P>
<A NAME="5912"></A><I>WWSympa</I> can also work without FastCGI, depending on the <B>use_fast_cgi</B> parameter 
(see <A HREF="node8.html#use-fastcgi">7.3.15</A>, page&nbsp;<A HREF="node8.html#use-fastcgi"><IMG  ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).

<P>
To run <A NAME="5915"></A><I>WWSympa</I> with FastCGI, you need to install :

<UL>
<LI><A NAME="5918"></A>mod_fastcgi  : the Apache module that provides <A NAME="5919"></A>FastCGI features

<P>
</LI>
<LI><A NAME="5920"></A><TT>FCGI</TT> : the Perl module used by <A NAME="5923"></A><I>WWSympa</I> 

<P>
</LI>
</UL>

<P>

<H1><A NAME="SECTION00830000000000000000">
7.3 wwsympa.conf parameters</A>
</H1>

<P>

<H2><A NAME="SECTION00831000000000000000">
7.3.1 arc_path</A>
</H2>

<P>
(Default value: <TT>/home/httpd/html/arc</TT>) 
<BR>
Where to store html archives. This parameter is used
        by the <A NAME="5927"></A><TT>archived.pl</TT> daemon. It is a good idea to install the archive
        outside the web hierarchy to prevent possible back doors in the access control
        powered by WWSympa. However, if Apache is configured with a chroot, you may
	have to install the archive in the Apache directory tree.

<P>

<H2><A NAME="SECTION00832000000000000000">
7.3.2 archive_default_index thrd | mail</A>
</H2>

<P>
(Default value: <TT>thrd</TT>) 
<BR>
The default index organization when entering web archives : either threaded or	
	chronological order.

<P>

<H2><A NAME="SECTION00833000000000000000">
7.3.3 archived_pidfile</A>
</H2>
	(Default value: <TT>archived.pid</TT>) 
<BR>
The file containing the PID of <A NAME="5932"></A><TT>archived.pl</TT>.

<P>

<H2><A NAME="SECTION00834000000000000000">
7.3.4 bounce_path</A>
</H2>
	(Default value: <TT>/var/bounce</TT>) 
<BR>
Root directory for storing bounces (non-delivery reports). This parameter
	is used mainly by the <A NAME="5936"></A><TT>bounced.pl</TT> daemon.

<P>

<H2><A NAME="SECTION00835000000000000000">
7.3.5 bounced_pidfile</A>
</H2>
	(Default value: <TT>bounced.pid</TT>) 
<BR>
The file containing the PID of <A NAME="5940"></A><TT>bounced.pl</TT>.

<P>

<H2><A NAME="SECTION00836000000000000000">
7.3.6 cookie_expire</A>
</H2>
	(Default value: <TT>0</TT>)
	Lifetime (in minutes) of HTTP cookies. This is the default value
	when not set explicitly by users.

<P>

<H2><A NAME="SECTION00837000000000000000">
7.3.7 cookie_domain</A>
</H2>
	(Default value: <TT>localhost</TT>) 
<BR>
Domain for the HTTP cookies. If beginning with a dot ('.'),
	the cookie is available within the specified internet domain.
	Otherwise, for the specified host. Example : 
		<PRE>
		   cookie_domain cru.fr
		   cookie is available for host 'cru.fr'

		   cookie_domain .cru.fr
		   cookie is available for any host within 'cru.fr' domain
</PRE>
	The only reason for replacing the default value would be where
	<A NAME="5945"></A><I>WWSympa</I>'s authentication process is shared with an application
	running on another host.

<P>

<H2><A NAME="SECTION00838000000000000000">
7.3.8 default_home</A>
</H2>
	(Default value: <TT>home</TT>) 
<BR>
Organization of the WWSympa home page. If you have only a few lists,
	the default value `home' (presenting a list of lists organized by topic)
	should be replaced by `lists' (a simple alphabetical list of lists).

<P>

<H2><A NAME="SECTION00839000000000000000">
7.3.9 icons_url</A>
</H2>
	(Default value: <TT>/icons</TT>) 
<BR>
URL of WWSympa's icons directory.

<P>

<H2><A NAME="SECTION008310000000000000000">
7.3.10 log_facility</A>
</H2>

<P>
WWSympa will log using this facility. Defaults to <I>Sympa</I>'s syslog
        facility.
	Configure your syslog according to this parameter.

<P>

<H2><A NAME="SECTION008311000000000000000">
7.3.11 mhonarc</A>
</H2>
	(Default value: <TT>/usr/bin/mhonarc</TT>) 
<BR>
Path to the (superb) MhOnArc program. Required for html archives
	http://www.oac.uci.edu/indiv/ehood/mhonarc.html

<P>

<H2><A NAME="SECTION008312000000000000000">
7.3.12 htmlarea_url</A>
</H2>
	(Default value: <TT>undefined</TT>) 
<BR>
Relative URL to the (superb) online html editor HTMLarea. If you have installed javascript application you can use it
        when editing html document in the shared document repository. In order to activate this pluggin the value of this
        parameter should point to the root directory where HTMLarea is installed.  HTMLarea is a free opensource software you can download
        here : http://sf.net/projects/itools-htmlarea/

<P>

<H2><A NAME="SECTION008313000000000000000">
7.3.13 password_case sensitive | insensitive</A>
</H2>
	(Default value: <TT>insensitive</TT>) 
<BR>
If set to <B>insensitive</B>, WWSympa's password check will be insensitive.
	This only concerns passwords stored in Sympa database, not the ones in <A NAME="5954"></A>LDAP.

<P>
<B>Be careful :</B> in previous 3.xx versions of Sympa, passwords were 
	lowercased before database insertion. Therefore changing to case-sensitive 
	password checking could bring you some password checking problems.

<P>

<H2><A NAME="SECTION008314000000000000000">
7.3.14 title</A>
</H2>
	(Default value: <TT>Mailing List Service</TT>) 
<BR>
The name of your mailing list service. It will appear in
	the Title section of WWSympa.

<P>

<H2><A NAME="SECTION008315000000000000000"></A>
	<A NAME="use-fastcgi"></A>
<BR>
7.3.15 use_fast_cgi   0 | 1
</H2>
	(Default value: <TT>1</TT>) 
<BR>
Choice of whether or not to use FastCGI. On listes.cru.fr, using FastCGI 
        increases WWSympa performance by as much as a factor of 10. Refer to 
       	<A NAME="tex2html22"
  HREF="http://www.fastcgi.com/">http://www.fastcgi.com/</A>
and the Apache config section of this document for details about 
	FastCGI.

<P>

<H1><A NAME="SECTION00840000000000000000">
7.4 MhOnArc</A>
</H1>

<P>
MhOnArc is a neat little converter from mime messages to html. Refer to
<A NAME="tex2html23"
  HREF="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">http://www.oac.uci.edu/indiv/ehood/mhonarc.html</A>.

<P>
The long mhonarc resource file is used by <A NAME="5957"></A><I>WWSympa</I> in a particular way.
MhOnArc is called to produce not a complete html document, but only a part of it
to be included in a complete document (starting with <TT>&lt;</TT>HTML<TT>&gt;</TT> and terminating
with <TT>&lt;</TT>/HTML<TT>&gt;</TT> ;-) ).
The best way is to use the MhOnArc resource file 
provided in the <A NAME="5960"></A><I>WWSympa</I> distribution and to modify it for your needs.

<P>
The mhonarc resource file is named <A NAME="5963"></A><TT>mhonarc-ressources</TT>. 
You may locate this file either in 
<OL>
<LI><A NAME="5966"></A><TT>/home/sympa/expl/mylist/mhonarc-ressources</TT>
	in order to create a specific archive look for a particular list

<P>
</LI>
<LI>or <A NAME="5969"></A><TT>/home/sympa/etc/mhonarc-ressources</TT>

<P>
</LI>
</OL>

<P>

<H1><A NAME="SECTION00850000000000000000">
7.5 Archiving daemon</A>
</H1>
<A NAME="5972"></A><TT>archived.pl</TT> converts messages from <I>Sympa</I>'s spools 
and calls <A NAME="5976"></A><TT>mhonarc</TT> to create html versions (whose location is defined by the 
"arc_path" WWSympa parameter). You should probably install these archives 
outside the <I>Sympa</I> home_dir (<I>Sympa</I>'s initial choice for storing mail archives : 
<A NAME="5981"></A><TT>/home/sympa/expl/mylist</TT>). Note that the html archive 
contains a text version of each message and is totally separate from <I>Sympa</I>'s
main archive.

<OL>
<LI>create a directory according to the WWSympa "arc_path" parameter
    (must be owned by sympa, does not have to be in Apache space unless
    your server uses chroot)

<P>
</LI>
<LI>for each list, if you need a web archive, create a new web archive paragraph
    in the list configuration. Example :<PRE>
     web_archive
     access public|private|owner|listmaster|closed
     quota 10000
</PRE>

<P>
If web_archive is defined for a list, every message distributed by this list is copied
     to <A NAME="5985"></A><TT>/home/sympa/spool/outgoing/</TT>. (No need to create nonexistent subscribers to receive
     copies of messages). In this example disk quota for the archive is limited to 10 Mo.

<P>
</LI>
<LI>start <A NAME="5988"></A><TT>archived.pl</TT>.
<I>Sympa</I> and Apache

<P>
</LI>
<LI>check <A NAME="5992"></A><I>WWSympa</I> logs, or alternatively, start <A NAME="5995"></A><TT>archived.pl</TT> in debug mode (-d). 

<P>
</LI>
<LI>If you change mhonarc resources and wish to rebuild the entire archive 
using the new look defined for mhonarc, simply create an empty file named
".rebuild.mylist@myhost" in <A NAME="5998"></A><TT>/home/sympa/spool/outgoing</TT>, and make sure that
the owner of this file is <I>Sympa</I>. 

<P><PRE>
     example : su sympa -c "touch /home/sympa/spool/outgoing/.rebuild.sympa-fr@cru.fr"
</PRE>
You can also rebuild web archives from within the admin page of the list.

<P>
Furthermore, if you want to get list's archives, you can do it via the <A NAME="6002"></A><TT> List-admin menu-&gt; Archive Management</TT>
</LI>
</OL>

<P>

<H1><A NAME="SECTION00860000000000000000">
7.6 Database configuration</A>
</H1>

<P>
<A NAME="6005"></A><I>WWSympa</I> needs an RDBMS (Relational Database Management System) in order to
run. All database access is performed via the <I>Sympa</I> API. <I>Sympa</I> 
currently interfaces with <A NAME="tex2html24"
  HREF="http://www.mysql.net/">MySQL</A>, <A NAME="tex2html25"
  HREF="http://www.postgresql.pyrenet.fr/">PostgreSQL</A>, <A NAME="tex2html26"
  HREF="http://www.oracle.com/database/">Oracle</A>
and <A NAME="tex2html27"
  HREF="http://www.sybase.com/index_sybase.html">Sybase</A>.

<P>
A database is needed to store user passwords and preferences.
The database structure is documented in the <I>Sympa</I> documentation ;
scripts for creating it are also provided with the <I>Sympa</I> distribution
(in <A NAME="6012"></A><TT>script</TT>). 

<P>
User information (password and preferences) are stored in the &#171;User&#187; table.
User passwords stored in the database are encrypted using reversible
RC4 encryption controlled with the <A NAME="6015"></A><TT>cookie</TT> parameter,
since <A NAME="6018"></A><I>WWSympa</I> might need to remind users of their passwords. 
The security of <A NAME="6021"></A><I>WWSympa</I> rests on the security of your database. 

<P>

<HR>
<!--Navigation Panel-->
<A NAME="tex2html847"
  HREF="node9.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A> 
<A NAME="tex2html841"
  HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A> 
<A NAME="tex2html835"
  HREF="node7.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A> 
<A NAME="tex2html843"
  HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A> 
<A NAME="tex2html845"
  HREF="node23.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html848"
  HREF="node9.html">8. Sympa SOAP server</A>
<B> Up:</B> <A NAME="tex2html842"
  HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html836"
  HREF="node7.html">6. Sympa and its database</A>
 &nbsp <B>  <A NAME="tex2html844"
  HREF="node1.html">Contents</A></B> 
 &nbsp <B>  <A NAME="tex2html846"
  HREF="node23.html">Index</A></B> 
<!--End of Navigation Panel-->
<ADDRESS>
root
2004-09-10
</ADDRESS>
</BODY>
</HTML>