+ Apache, see the russian_apache.txt in the doc/ subdirectory.
+
+
+6. TRANSLATIONS
+---------------
+
+ In order to use translated versions of SquirrelMail, you need
+ to download and install locale packages that contain translations
+ that you want to use with SquirrelMail.
+
+ Locale packages can be downloaded from SquirrelMail SourceForge
+ project page.
+
+ http://sourceforge.net/project/showfiles.php?group_id=311&package_id=110388
+
+ 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 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
+ in order to get all gettext binary translations.
+
+ NOTE No.2: You might need to restart your webserver before using translations.
+ If you can't do that, install your translations _before_ you use SquirrelMail.
+
+
+7. PLUGINS
+----------
+
+ The SquirrelMail package includes some standard plugins. These plugins can be
+ enabled in the SquirrelMail configuration script.
+
+ Included plugins can use additional configuration files:
+ * change_password
+ configuration file is required. Without it plugin defaults to invalid
+ backend. See plugins/change_password/README
+ * filters, fortune, mail_fetch, newmail, translate
+ configuration files are optional. See README files in plugin directories.
+ * squirrelspell
+ configuration is stored in plugins/squirrelspell/sqspell_config.php
+ The default configuration might not work at your server.
+ * administrator
+ plugin must be setup correctly in order to detect administrative user.
+ See plugins/administrator/INSTALL