Next: 11. Customizing Sympa/WWSympa Up: Sympa Mailing Lists Management Software version Previous: 9. Authorization scenarios Contents Index
Subsections

- 10.1 How to create a virtual robot
- 10.2 robot.conf
  - 10.2.1 Robot customization

#
10. Virtual robot

Sympa is designed to manage multiple distinct mailing list servers on a single host with a single Sympa installation. Sympa virtual robots are like Apache virtual hosting. Sympa virtual robot definition includes a specific email address for the robot itself and its lists and also a virtual http server. Each robot provides access to a set of lists, each list is related to only one robot.

Most configuration parameters can be define for each robot except general Sympa installation parameters (binary and spool location, smtp engine, antivirus plugging,...).

The Virtual robot name as defined in Sympa documentation and configuration file refers to the Internet domaine of the Virtual robot.

# 10.1 How to create a virtual robot

You don't need to install several Sympa servers. A single `sympa.pl` 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.

- The DNS must be configured to define a new mail exchanger record (MX) to route message to your server. A new host (A record) or alias (CNAME) are mandatory to define the new web server.
- Configure your MTA (sendmail, postfix, exim, ...) to accept incoming messages for the new robot domain. Add mail aliases for the robot :

  Examples (with sendmail):

      sympa@your.virtual.domain:      "| /home/sympa/bin/queue sympa@your.virtual.domain"
      listmaster@your.virtual.domain: "| /home/sympa/bin/queue listmaster@your.virtual.domain"

- Define a virtual host in your HTTPD server. The fastcgi servers defined in the common section of you httpd server can be used by each virtual host. You don't need to run dedicated fascgi server for each virtual robot.

  Examples:

      FastCgiServer /home/sympa/bin/wwsympa.fcgi -processes 3 -idle-timeout 120
      .....
      <VirtualHost 195.215.92.16>
        ServerAdmin webmaster@your.virtual.domain
        DocumentRoot /var/www/your.virtual.domain
        ServerName your.virtual.domain

        <Location /wws>
           SetHandler fastcgi-script
        </Location>

        ScriptAlias /wws /home/sympa/bin/wwsympa.fcgi

      </VirtualHost>

- Create a `robot.conf` for the virtual robot (current web interface does not provide Virtual robot creation yet).

# 10.2 robot.conf

A robot is named by its domain, let's say my.domain.organd defined by a directory `/home/sympa/etc/my.domain.org`. This directory must contain at least a `robot.conf` file. This files has the same format as `/etc/sympa.conf` (have a look at robot.conf in the sample dir). Only the following parameters can be redefined for a particular robot :

- `http_host`
  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 you are running multiple Virtual robots on the same host.

      Examples: \\
      	http_host  myhost.mydom
      	http_host  myhost.mydom/sympa

- `wwsympa_url`
  The base URL of WWSympa

- `cookie_domain`

- `email`

- `title`

- `default_home`

- `create_list`

- `lang`

- `log_smtp`

- `listmaster`

- `max_size`

- `dark_color`, `light_color`, `text_color`, `bg_color`, `error_color`, `selected_color`, `shaded_color`

These settings overwrite the equivalent global parameter defined in `/etc/sympa.conf` for my.domain.orgrobot ; the main `listmaster` 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.

## 10.2.1 Robot customization

If needed, you can customize each virtual robot using its set of templates and authorization scenarios.

`/home/sympa/etc/my.domain.org/wws_templates/`, `/home/sympa/etc/my.domain.org/templates/`, `/home/sympa/etc/my.domain.org/scenari/` directories are searched when loading templates or scenari before searching into `/home/sympa/etc` and `/home/sympa/bin/etc`. This allows to define different privileges and a different GUI for a Virtual Robot.

Next: 11. Customizing Sympa/WWSympa Up: Sympa Mailing Lists Management Software version Previous: 9. Authorization scenarios Contents Index