|
@@ -165,11 +165,14 @@ b. Setting up directories
|
|
|
|
|
|
c. Setting up SquirrelMail
|
|
|
|
|
|
- There are two ways to configure SquirrelMail. In the config/ directory,
|
|
|
+ There are three ways to configure SquirrelMail. In the config/ directory,
|
|
|
there is a perl script called conf.pl that will aid you in the
|
|
|
configuration process. This is the recommended way of handling
|
|
|
the config.
|
|
|
|
|
|
+ There's also a plugin called 'administrator' for the webinterface but you'll
|
|
|
+ have to be able to at least log in to SquirrelMail first.
|
|
|
+
|
|
|
You can also copy the config/config_default.php file to config/config.php
|
|
|
and edit that manually.
|
|
|
|
|
@@ -211,11 +214,11 @@ c. Setting up SquirrelMail
|
|
|
|
|
|
Each translation contains an install script that copies the required files
|
|
|
into their appropriate locations. If you can't run that script, you can
|
|
|
- extract the contents of translation packages into your SquirrelMail
|
|
|
+ extract the contents of a translation package into your SquirrelMail
|
|
|
directory.
|
|
|
|
|
|
NOTE No.1: *-src.tar.gz, *-src.tar.bz2 and *-src.zip archives do not contain
|
|
|
- compiled translation files. You will need to run the compilelocales script
|
|
|
+ compiled translation files. You will need to run the "compilelocales" script
|
|
|
in order to get all gettext binary translations.
|
|
|
|
|
|
NOTE No.2: You might need to restart your webserver before using translations.
|