After release of 6.2, several changes on templates are made. If you have customized templates with earlier version, you should check if web interface will work correctly after upgrading, and reapply customization to new templates as necessity.
Following subsections describe changes by particular versions of 6.2.x. If you are planning to upgrade from version prior to 6.2, see also sections below.
If you have set
robot.conf, you may have to change it.
http_hostis identical to the host part of
wwsympa_urlparameter, it may simply be removed. For example,
wwsympa_url http://web .example.org/sympa http_host web.example.org
may be changed to
wwsympa_url_localparameter. For example,
wwsympa_url http://web.example.org/sympa http_host backend.example.org
should be modified as
wwsympa_url http://web.example.org/sympa wwsympa_url_local http://backend.example.org/sympa
message.footer.tt2of the family according to new format (See “Family unsubscription” for details).
Some scenarios and list creation templates for “intranet” use cases were made
optional: They have been moved into
If you have to use following scenario files, copy those files in
samples/intranet/scenari/ to appropriate
If you have to use these files in a list creation template, copy those files
samples/intranet/create_list_templates to a subdirectory of appropriate
Inclusion feature of members, owners or moderators has been reconstructed. Slightly long time can be spent to refresh inclusion of users entirely at the first time just after upgrade.
Perl version 5.10.1 or later will be supported.
emailAddressattribute in subject DN. Note that earlier efforts getting attribute such as
The “default” scenario files named
*.default (regular file or symbolic
link) are no longer available: Default list scenariios have to be
specified by parameters in
For details on parameters see
“Default privileges for the lists”
sympa.conf(5) manual page.
Previous default settings using symbolic links are automatically migrated
during upgrading process. However you should review the changes in
WWSympa and SympaSOAP:
trusted_applications.confwhile it is there in
$SYSCONFDIR, the latter will be used. Previously in such case, the latter was ignored and only built-in authnetication was enabled.
RC4 reversible encryption of password storage in database using
Crypt::CipherSaber was dropped. If you have been using it, run
rehash passwords stored in database.
bcrypt, more secure hash function. See “Upgrading password storage on earlier version” for details.
bind_dnparameter. Previously, the second search operation to retrieve user entry was performed under the privilege of the user of their own.
db_hostparameter explicitly, add a line
For details see the instruction.
host list parameter was deprecated. If you have used this parameter:
hostlist parameter (Note: replace
# mkdir -m 755 $SYSCONFDIR/<host> # touch $SYSCONFDIR/<host>/robot.conf # chown -R sympa:sympa $SYSCONFDIR/<host> # mkdir -m 750 $EXPLDIR/<host> # chown sympa:sympa $EXPLDIR/<host>
And rename list
listname@host, using web interface or
sympa.pl command line tool.
list_aliases.tt2and may have to regenerate alias file after upgrading as:
# sympa.pl --make_alias_file --robot <mail domain> # sympa_newaliases.pl --domain <mail domain>
Note that you are recommended to back up database and older alias files in advance.
If you managed multiple domains and used web interface,
wwsympa_url parameter in each
robot.conf file is now mandatory.
Though it will be automatically added during upgrading process, if you used HTTPS protocol,
you may have to edit value of
wwsympa_url parameter in each
sympa.pl --upgradecrashes due to undefined variable
$pictures_dir, remove following files and retry:
sympa.conf.binplaced in the same directory as
robot.conf.binplaced in the same directory as each
robot.conffile, if any.
access_web_archive.*scenarios are renamed to
archive_web_access.*. If you have customized any of these scenarios, you have to rename them under config directory.
css_path parameters in
robot.conf are no longer
available: Those in
sympa.conf (if any) are used.
If you have specified
css_path parameter by each
you have to move each directory to subdirectory named by domain
under directory specified by
css_path directory in
configureoptions and parameters
If you have used none of
--with-staticdir configure option,
static_content_path parameter nor
no changes described below are required.
If you have built Sympa from source and have specified
configure option, you might want to specify
$ ./configure --with-staticdir=DIR (...)
$ ./configure --with-staticdir=DIR --with-cssdir=DIR/css --with-picturesdir=DIR/pictures (...)
static_content_path DIR css_path DIR/css pictures_path DIR/pictures
static_content_url PATH css_url PATH/css pictures_url PATH/pictures
It is not forced, but it is recommended to upgrade password storage format of
web interface using
bcrypt, more secure hash function. See
“Upgrading password storage on earlier version”
Data sources: “
%” sign in SQL data source no longer need escaping by
duplicating it, i.e. “
%%”. Administrators on the sites allowing SQL
data sources are recommended to check data source settings and modify
them as necessity.
WWSympa: FastCGI support became mandatory. CGI mode was deprecated. See “Configure HTTP server for details about configuration.
Several changes in Sympa 6.2 require to perform specific operations when upgrading. Here is the ordered list of operations to perform.
[Source distribution only] Check the options for
As some Sympa binaries have been renamed, your sympa init script have to be updated. Please make sure your configure options have been correctly set, so that this script ends up in the correct location. See “Run configure script” for details.
deprecated. Use –with-aliases_file instead.
--with-postmap_arg was removed.
# sympa_wizard.pl --check # Update dependent modules # sympa.pl --upgrade_config_location # move existing configs to /etc/sympa/ directory # sympa.pl --upgrade # merge sympa.conf and wwsympa.conf
Commands after upgrade:
These are always needed you are using either binary distribution or source distribution.
# upgrade_bulk_spool.pl # move messages stored in database to filesystem # upgrade_send_spool.pl # move messages sent through web interface to the new format
After the process above, the following changes will have occured:
sympa.confis now located in a
wwsympa.confwill have been merged into
wwsympa.confwill no longer be used.
sympa.conf remaining will have been stripped of any “
parameters, to prevent you from having a messed up web interface.
robot.confwill have had the same treatment as
sympa.conf(copy, then stripped of
sympa.confwill have need copied to “
Indeed, as most of the Sympa templates have been changed for the new skin, your customizations could not be compliant to the new web interface. You should see how to reintroduce them to the new templates.
Additionally, you may have to fix up configuration manually:
The default is “
off”: To enable archiving, it must be set to “
robot.conf or each list
If you have used
virtualwrapper, it was replaced with new programs
sympa_newaliases.pl and its wrapper: You may have to add new parameters
Renamed list parameters:
Deprecated list parameter:
user_data_source. All subscribers are stored in database.
subscribers file in list directory will no longer be imported.
Administrators are strongly recommended to check new configuration. Customized scenarios, list creation templeates and edit_list.conf will never be upgraded automatically.
Since there are big changes after 5.4.x, we recommend that recent version of Sympa will be installed into new machine, or at least will be installed under separate directory, keeping installation and data of earlier version.
# /etc/rc.d/init.d/sympa stop
Then back up everything.
Note that you should also backup init script of earlier version, because it may be overwritten by installing recent version (if you will install recent version to the same machine).
Install recent version of Sympa.
Copy configuration files and database:
Copy configuration files
earlier version to recent version. Then edit them to fix up
configuration (including name of database below).
Queued messages in spools of earlier version should be copied into the new location. Their formats will be changed later.
Restore entire database content as a new database (e.g. naming it
sympa6” instead of “
sympa”). Because, succeeding process
will upgrade content and structure of database and those changes are
AL32UTF8. Even if it does not, Sympa will work, however it is desirable. To know how to convert your database to be Unicode-aware, please consult to documentation of database server.
Upgrade configuration and data:
# sympa.pl --upgrade --from=5.4.7
5.4.7 above must be replaced with the version number you
are updating from. Doing this, configuration and database structure
will be upgraded.
Upgrade format of web interface password in the database. See “Upgrading password storage on earlier version”.
(Not yet written)
Theme originally designed by orderedlist