Contents

• 1. Presentation
  • 1.1 License
  • 1.2 Features
  • 1.3 Project directions
  • 1.4 History
  • 1.5 Authors and credits
  • 1.6 Mailing lists and support
  
  
• 2. what does Sympa consist of ?
  • 2.1 Organization
  • 2.2 Binaries
  • 2.3 Configuration files
  • 2.4 Spools
  • 2.5 Roles and privileges
    • 2.5.1 (Super) listmasters
    • 2.5.2 (Robot) listmasters
    • 2.5.3 Privileged list owners
    • 2.5.4 (Basic) list owners
    • 2.5.5 Moderators (also called Editors)
    • 2.5.6 Subscribers (or list members)
  
  
• 3. Installing Sympa
  • 3.1 Obtaining Sympa, related links
  • 3.2 Prerequisites
    • 3.2.1 System requirements
    • 3.2.2 Install Berkeley DB (NEWDB)
    • 3.2.3 Install PERL and CPAN modules
    • 3.2.4 Required CPAN modules
    • 3.2.5 Create a UNIX user
  • 3.3 Compilation and installation
    • 3.3.1 Choosing directory locations
  • 3.4 Robot aliases
  • 3.5 Logs
  
  
• 4. Running Sympa
  • 4.1 sympa.pl
  • 4.2 INIT script
  • 4.3 Stopping Sympa and signals
  
  
• 5. Upgrading Sympa
  • 5.1 Incompatible changes
  • 5.2 CPAN modules update
  • 5.3 Database structure update
  • 5.4 Preserving your customizations
  • 5.5 Running 2 Sympa versions on a single server
  • 5.6 Moving to another server
  
  
• 6. Mail aliases
  • 6.1 Robot aliases
  • 6.2 List aliases
  • 6.3 Alias manager
  • 6.4 Virtual domains
  
  
• 7. sympa.conf parameters
  • 7.1 Site customization
    • 7.1.1 domain
    • 7.1.2 email
    • 7.1.3 listmaster
    • 7.1.4 listmaster_email
    • 7.1.5 wwsympa_url
    • 7.1.6 soap_url
    • 7.1.7 spam_protection
    • 7.1.8 web_archive_spam_protection
    • 7.1.9 color_0, color_1 .. color_15
    • 7.1.10 dark_color light_color text_color bg_color error_color selected_color shaded_color
    • 7.1.11 logo_html_definition
    • 7.1.12 css_path
    • 7.1.13 css_url
    • 7.1.14 cookie
    • 7.1.15 create_list
    • 7.1.16 global_remind
  • 7.2 Directories
    • 7.2.1 home
    • 7.2.2 etc
  • 7.3 System related
    • 7.3.1 syslog
    • 7.3.2 log_level
    • 7.3.3 log_socket_type
    • 7.3.4 pidfile
    • 7.3.5 umask
  • 7.4 Sending related
    • 7.4.1 distribution_mode
    • 7.4.2 maxsmtp
    • 7.4.3 log_smtp
    • 7.4.4 max_size
    • 7.4.5 misaddressed_commands
    • 7.4.6 misaddressed_commands_regexp
    • 7.4.7 nrcpt
    • 7.4.8 avg
    • 7.4.9 sendmail
    • 7.4.10 sendmail_args
    • 7.4.11 sendmail_aliases
    • 7.4.12 rfc2369_header_fields
    • 7.4.13 remove_headers
    • 7.4.14 anonymous_headers_fields
    • 7.4.15 list_check_smtp
    • 7.4.16 list_check_suffixes
    • 7.4.17 urlize_min_size
  • 7.5 Quotas
    • 7.5.1 default_share6690">./configure on the test server side :

      ./configure --prefix=/home/sympa-dev \
                  --with-confdir=/home/sympa-dev/etc \
                  --with-mandir=/home/sympa-dev/man \
                  --with-initdir=/home/sympa-dev/init \
      	    --with-piddir=/home/sympa-dev/pid
                  --with-lockdir=/home/sympa-dev/lock \
                  --with-sendmail_aliases=/home/sympa-dev/etc/sympa_aliases
      

      You can also customize more parameters via the /home/sympa-dev/etc/sympa.conf file.

      If you wish to share the same lists in both Sympa instances, then some parameters should have the same value : home, db_name, arc_path

      
      5.6 Moving to another server

      If you're upgrading and moving to another server at the same time, we recommend you first to stop the operational service, move your data and then upgrade Sympa on the new server. This will guarantee that Sympa upgrade procedures have been applied on the data.

      The migration process requires that you move the following data from the old server to the new one :

      • the user database. If using mysql you can probably just stop mysqld and copy the /var/lib/mysql/sympa/ directory to the new server.

      • the /home/sympa/expl directory that contains list config

      • the directory that contains the spools

      • the directory and /etc/sympa.conf and wwsympa.conf. Sympa new installation create a file /etc/sympa.conf (see 7) and initialize randomly the cookie parameter. Changing this parameter will break all passwords. When upgrading Sympa on a new server take care that you start with the same value of this parameter, otherwise you will have troubles !

      • the web archives

      In some case, you may want to install the new version and run it for a few days before switching the existing service to the new Sympa server. In this case perform a new installation with an empty database and play with it. When you decide to move the existing service to the new server :

      1. stop all sympa processus on both servers,
      2. transfert the database
      3. edit the /data_structure.version on the new server ; change the version value to reflect the old number
      4. start sympa.pl, it will upgrade the database structure according the hop you do.
      ./usr/share/doc/sympa/html/node1.html0000644000000000000000000014042311032175371016366 0ustar rootroot
      

      Contents

      • 1. Presentation
        • 1.1 License
        • 1.2 Features
        • 1.3 Project directions
        • 1.4 History
        • 1.5 Authors and credits
        • 1.6 Mailing lists and support
        
        
      • 2. what does Sympa consist of ?
        • 2.1 Organization
        • 2.2 Binaries
        • 2.3 Configuration files
        • 2.4 Spools
        • 2.5 Roles and privileges
          • 2.5.1 (Super) listmasters
          • 2.5.2 (Robot) listmasters
          • 2.5.3 Privileged list owners
          • 2.5.4 (Basic) list owners
          • 2.5.5 Moderators (also called Editors)
          • 2.5.6 Subscribers (or list members)
        
        
      • 3. Installing Sympa
        • 3.1 Obtaining Sympa, related links
        • 3.2 Prerequisites
          • 3.2.1 System requirements
          • 3.2.2 Install Berkeley DB (NEWDB)
          • 3.2.3 Install PERL and CPAN modules
          • 3.2.4 Required CPAN modules
          • 3.2.5 Create a UNIX user
        • 3.3 Compilation and installation
          • 3.3.1 Choosing directory locations
        • 3.4 Robot aliases
        • 3.5 Logs
        
        
      • 4. Running Sympa
        • 4.1 sympa.pl
        • 4.2 INIT script
        • 4.3 Stopping Sympa and signals
        
        
      • 5. Upgrading Sympa
        • 5.1 Incompatible changes
        • 5.2 CPAN modules update
        • 5.3 Database structure update
        • 5.4 Preserving your customizations
        • 5.5 Running 2 Sympa versions on a single server
        • 5.6 Moving to another server
        
        
      • 6. Mail aliases
        • 6.1 Robot aliases
        • 6.2 List aliases
        • 6.3 Alias manager
        • 6.4 Virtual domains
        
        
      • 7. sympa.conf parameters
        • 7.1 Site customization
          • 7.1.1 domain
          • 7.1.2 email
          • 7.1.3 listmaster
          • 7.1.4 listmaster_email
          • 7.1.5 wwsympa_url
          • 7.1.6 soap_url
          • 7.1.7 spam_protection
          • 7.1.8 web_archive_spam_protection
          • 7.1.9 color_0, color_1 .. color_15
          • 7.1.10 dark_color light_color text_color bg_color error_color selected_color shaded_color
          • 7.1.11 logo_html_definition
          • 7.1.12 css_path
          • 7.1.13 css_url
          • 7.1.14 cookie
          • 7.1.15 create_list
          • 7.1.16 global_remind
        • 7.2 Directories
          • 7.2.1 home
          • 7.2.2 etc
        • 7.3 System related
          • 7.3.1 syslog
          • 7.3.2 log_level
          • 7.3.3 log_socket_type
          • 7.3.4 pidfile
          • 7.3.5 umask
        • 7.4 Sending related
          • 7.4.1 distribution_mode
          • 7.4.2 maxsmtp
          • 7.4.3 log_smtp
          • 7.4.4 max_size
          • 7.4.5 misaddressed_commands
          • 7.4.6 misaddressed_commands_regexp
          • 7.4.7 nrcpt
          • 7.4.8 avg
          • 7.4.9 sendmail
          • 7.4.10 sendmail_args
          • 7.4.11 sendmail_aliases
          • 7.4.12 rfc2369_header_fields
          • 7.4.13 remove_headers
          • 7.4.14 anonymous_headers_fields
          • 7.4.15 list_check_smtp
          • 7.4.16 list_check_suffixes
          • 7.4.17 urlize_min_size
        • 7.5 Quotas
          • 7.5.1 default_share6690">./configure on the test server side :

            ./configure --prefix=/home/sympa-dev \
                        --with-confdir=/home/sympa-dev/etc \
                        --with-mandir=/home/sympa-dev/man \
                        --with-initdir=/home/sympa-dev/init \
            	    --with-piddir=/home/sympa-dev/pid
                        --with-lockdir=/home/sympa-dev/lock \
                        --with-sendmail_aliases=/home/sympa-dev/etc/sympa_aliases
            

            You can also customize more parameters via the /home/sympa-dev/etc/sympa.conf file.

            If you wish to share the same lists in both Sympa instances, then some parameters should have the same value : home, db_name, arc_path

            
            5.6 Moving to another server

            If you're upgrading and moving to another server at the same time, we recommend you first to stop the operational service, move your data and then upgrade Sympa on the new server. This will guarantee that Sympa upgrade procedures have been applied on the data.

            The migration process requires that you move the following data from the old server to the new one :

            • the user database. If using mysql you can probably just stop mysqld and copy the /var/lib/mysql/sympa/ directory to the new server.

            • the /home/sympa/expl directory that contains list config

            • the directory that contains the spools

            • the directory and /etc/sympa.conf and wwsympa.conf. Sympa new installation create a file /etc/sympa.conf (see 7) and initialize randomly the cookie parameter. Changing this parameter will break all passwords. When upgrading Sympa on a new server take care that you start with the same value of this parameter, otherwise you will have troubles !

            • the web archives

            In some case, you may want to install the new version and run it for a few days before switching the existing service to the new Sympa server. In this case perform a new installation with an empty database and play with it. When you decide to move the existing service to the new server :

            1. stop all sympa processus on both servers,
            2. transfert the database
            3. edit the /data_structure.version on the new server ; change the version value to reflect the old number
            4. start sympa.pl, it will upgrade the database structure according the hop you do.
            ./usr/share/doc/sympa/html/node1.html0000644000000000000000000014042311032175371016366 0ustar rootroot
            

            Contents

            • 1. Presentation
              • 1.1 License
              • 1.2 Features
              • 1.3 Project directions
              • 1.4 History
              • 1.5 Authors and credits
              • 1.6 Mailing lists and support
              
              
            • 2. what does Sympa consist of ?
              • 2.1 Organization
              • 2.2 Binaries
              • 2.3 Configuration files
              • 2.4 Spools
              • 2.5 Roles and privileges
                • 2.5.1 (Super) listmasters
                • 2.5.2 (Robot) listmasters
                • 2.5.3 Privileged list owners
                • 2.5.4 (Basic) list owners
                • 2.5.5 Moderators (also called Editors)
                • 2.5.6 Subscribers (or list members)
              
              
            • 3. Installing Sympa
              • 3.1 Obtaining Sympa, related links
              • 3.2 Prerequisites
                • 3.2.1 System requirements
                • 3.2.2 Install Berkeley DB (NEWDB)
                • 3.2.3 Install PERL and CPAN modules
                • 3.2.4 Required CPAN modules
                • 3.2.5 Create a UNIX user
              • 3.3 Compilation and installation
                • 3.3.1 Choosing directory locations
              • 3.4 Robot aliases
              • 3.5 Logs
              
              
            • 4. Running Sympa
              • 4.1 sympa.pl
              • 4.2 INIT script
              • 4.3 Stopping Sympa and signals
              
              
            • 5. Upgrading Sympa
              • 5.1 Incompatible changes
              • 5.2 CPAN modules update
              • 5.3 Database structure update
              • 5.4 Preserving your customizations
              • 5.5 Running 2 Sympa versions on a single server
              • 5.6 Moving to another server
              
              
            • 6. Mail aliases
              • 6.1 Robot aliases
              • 6.2 List aliases
              • 6.3 Alias manager
              • 6.4 Virtual domains
              
              
            • 7. sympa.conf parameters
              • 7.1 Site customization
                • 7.1.1 domain
                • 7.1.2 email
                • 7.1.3 listmaster
                • 7.1.4 listmaster_email
                • 7.1.5 wwsympa_url
                • 7.1.6 soap_url
                • 7.1.7 spam_protection
                • 7.1.8 web_archive_spam_protection
                • 7.1.9 color_0, color_1 .. color_15
                • 7.1.10 dark_color light_color text_color bg_color error_color selected_color shaded_color
                • 7.1.11 logo_html_definition
                • 7.1.12 css_path
                • 7.1.13 css_url
                • 7.1.14 cookie
                • 7.1.15 create_list
                • 7.1.16 global_remind
              • 7.2 Directories
                • 7.2.1 home
                • 7.2.2 etc
              • 7.3 System related
                • 7.3.1 syslog
                • 7.3.2 log_level
                • 7.3.3 log_socket_type
                • 7.3.4 pidfile
                • 7.3.5 umask
              • 7.4 Sending related
                • 7.4.1 distribution_mode
                • 7.4.2 maxsmtp
                • 7.4.3 log_smtp
                • 7.4.4 max_size
                • 7.4.5 misaddressed_commands
                • 7.4.6 misaddressed_commands_regexp
                • 7.4.7 nrcpt
                • 7.4.8 avg
                • 7.4.9 sendmail
                • 7.4.10 sendmail_args
                • 7.4.11 sendmail_aliases
                • 7.4.12 rfc2369_header_fields
                • 7.4.13 remove_headers
                • 7.4.14 anonymous_headers_fields
                • 7.4.15 list_check_smtp
                • 7.4.16 list_check_suffixes
                • 7.4.17 urlize_min_size
              • 7.5 Quotas
                • 7.5.1 default_share6690">./configure on the test server side :

                  ./configure --prefix=/home/sympa-dev \
                              --with-confdir=/home/sympa-dev/etc \
                              --with-mandir=/home/sympa-dev/man \
                              --with-initdir=/home/sympa-dev/init \
                  	    --with-piddir=/home/sympa-dev/pid
                              --with-lockdir=/home/sympa-dev/lock \
                              --with-sendmail_aliases=/home/sympa-dev/etc/sympa_aliases
                  

                  You can also customize more parameters via the /home/sympa-dev/etc/sympa.conf file.

                  If you wish to share the same lists in both Sympa instances, then some parameters should have the same value : home, db_name, arc_path

                  
                  5.6 Moving to another server

                  If you're upgrading and moving to another server at the same time, we recommend you first to stop the operational service, move your data and then upgrade Sympa on the new server. This will guarantee that Sympa upgrade procedures have been applied on the data.

                  The migration process requires that you move the following data from the old server to the new one :

                  • the user database. If using mysql you can probably just stop mysqld and copy the /var/lib/mysql/sympa/ directory to the new server.

                  • the /home/sympa/expl directory that contains list config

                  • the directory that contains the spools

                  • the directory and /etc/sympa.conf and wwsympa.conf. Sympa new installation create a file /etc/sympa.conf (see 7) and initialize randomly the cookie parameter. Changing this parameter will break all passwords. When upgrading Sympa on a new server take care that you start with the same value of this parameter, otherwise you will have troubles !

                  • the web archives

                  In some case, you may want to install the new version and run it for a few days before switching the existing service to the new Sympa server. In this case perform a new installation with an empty database and play with it. When you decide to move the existing service to the new server :

                  1. stop all sympa processus on both servers,
                  2. transfert the database
                  3. edit the /data_structure.version on the new server ; change the version value to reflect the old number
                  4. start sympa.pl, it will upgrade the database structure according the hop you do.
                  ./usr/share/doc/sympa/html/node1.html0000644000000000000000000014042311032175371016366 0ustar rootroot