<A NAME='installwwsympa'>
choose to use or not FastCGI. On listes.cru.fr using FastCGI with WWSympa fasten up to 10 times. Refer to http://www.fastcgi.com/ and the apache config section of this document for details about FastCGI.
WWSympa will log using this facility. Configure your syslog according to this parameter
Location of WWSympa install directory in your filesystem.
World Wide Sympa's corresponding URL.
Location of your sympa configuration file.
The long mhonarc ressource file is used in a special way with World Wide Sympa because mhonarc is used to produce not html document but only part of them that are included in a complete document starting with <HTML> and terminating with </HTML> ;-) The best way to start is to use the MhOnArc ressource file as provided in World Wide Sympa distribution.
The mhonarc ressources file name is specified in wwsympa.conf "mhonarc_ressources" parameter. You may locate this file either - in sympa/expl/[listname]/[mhonarc_ressources] in order to create specific archive look for one list or - in sympa/wwsympa/[mhonarc_ressources].[lang]
where [lang] is the langage specified in [listname] configuration file or by
default the site langage default specified in sympa.conf, Please refer to
3, page .
archived.pl is intended to convert messages comming from sympa spools and to call mhonarc to create html version located according to the "arc_path" wwsympa parameter. You should probably install thoses archives elsewhere than sympa home_dir. (we think the initial choice of Sympa to store mail archive in the ~sympa/expl/[listname] directory). Note that html archive containt a txt version of any message and are totaly separed from old Sympa archive.
web_archive access public|private|owner|listmaster|closed
This paramter is not yet defined by scenario scheme but it will If web_archive is define for a list any message distributed by this list is copied in the queueoutgoing spool. You do not need to create crazy subscriber that receive the archive by mail.
example : su sympa -c "touch ~sympa/spool/outgoing/.rebuild.sympa-fr@cru.fr"
If you chose to run wwsympa.fcgi a simple CGI, you just need to script alias it.
Example : ScriptAlias /wws /home/sympa/wwsympa/wwsympa.fcgi
Running FastCGI will provide much faster responses from your server and lower load (to understand why, read http://www.fastcgi.com/fcgi-devkit-2.1/doc/fcgi-perf.htm)
Example : ScriptAlias /wws /home/sympa/wwsympa/wwsympa.fcgi AppClass /home/sympa/wwsympa/wwsympa.fcgi <Location /wws> SetHandler fastcgi-script </Location>
World Wide Sympa needs a RDBMS (Relational Database Management System) to run. All database access is performed via Sympa API. Sympa currently interfaces with MySQL, PostgreSQL, Oracle and Sybase.
Database is needed to store user passwords and preferences. The database structure is documented in Sympa documentation ; scripts for creating it are also provided with Sympa distribution (in script).
User information (password and prefs) are stored in «User» table. User passwords stored in database are NOT CRYPTED since World Wide Sympa might need to remind users with their passwords. World Wide Sympa security relies on your database
Not available yet
edit_list_request (not yet terminated)
Summary of main properties
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 \# all other parameters can be changed by simple owners default owner
Privileged owners are owner witch paragraph definition in list config file contain a line : "profile privileged".
The following rules are hardcoded in wwsympa :
The goal is to define two trust level for owners (some can just edit gadget like "custom_subject", some others can edit important parameters, but keep control of crutial parameters like the list of privileged owners or user_data_sources. So owners can change there e-mail (asking to a privileged owner to do it), but they can't give away the list mangement responsability to someone else without refering to listmaster.
World Wide Sympa allows bounces (non-delivery reports) management. This prevents list owners from receiving each bounce (1 per message sent to a bouncing subscriber) in their own mailbox. Without an automatic processing of bounces, list owners either become mad or just delete them without further attention.
Bounces are received at <listname>-owner address, which should be sent to "bouncequeue" prog through aliases :
<listname>-owner: "|/home/sympa/bin/bouncequeue <listname>"
"bouncequeue", distributed with Sympa, stores bounces in a dedicated spool (see "queuebounce" param in sympa.conf).
Bounces are then processed by a daemon, "bounced.pl" provided with World Wide Sympa. This daemon analyses bounces to find out what email addresses is concerned and what kind of error was generated. If bouncing address matches a subscriber's address, information are stored in Sympa database (in "user_table"). Moreover, latest bounce itself is archived in "bounce_path"/<listname>/<email> ("bounce_path" is defined in wwsympa.conf).
When reviewing a list, bouncing addresses are tagged as "bouncing" ; you may access further information such as : first and last bounces date, number of received bounces for the address, the last bounce itself.
Further development of Sympa/World Wide Sympa should allow automatic deletion of bouncing addresses.