From: <pdo...@us...> - 2008-10-04 21:51:23
|
Revision: 13294 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13294&view=rev Author: pdontthink Date: 2008-10-04 21:51:17 +0000 (Sat, 04 Oct 2008) Log Message: ----------- Small changes Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2008-09-28 14:58:07 UTC (rev 13293) +++ trunk/documentation/admin/admin.sgml 2008-10-04 21:51:17 UTC (rev 13294) @@ -1682,8 +1682,8 @@ <tt/zlib.output_compression/ in <tt/php.ini/. <item>SquirrelMail has the <url url="http://squirrelmail.org/plugin_view.php?id=19" name="Gzip - Compressed Output"> plugin that can compress certain pages, but won't - compress much. It does help, but one of the others is suggested instead. + Compressed Output"> plugin that enables compression of output + in the same way that PHP does (see above), but only for SquirrelMail. </itemize> <sect2>Condensation This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2008-11-25 04:27:04
|
Revision: 13331 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13331&view=rev Author: pdontthink Date: 2008-11-25 04:26:54 +0000 (Tue, 25 Nov 2008) Log Message: ----------- Minor wording Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2008-11-24 20:24:04 UTC (rev 13330) +++ trunk/documentation/admin/admin.sgml 2008-11-25 04:26:54 UTC (rev 13331) @@ -1253,8 +1253,10 @@ <p> On sites with many users you might want to store your user data in a database instead of in files. SquirrelMail can be configured to do this. Note, however, -that some SquirrelMail plugins are designed to use different files for users' -data storage and won't be able to use database to store users' data. +that some SquirrelMail plugins are designed to use different files for user +data storage and won't be able to use the database, so it is strongly +recommended to make sure you have a correctly configured data directory even +when using a database as explained here. Methods for storing both personal address books and user preferences in a database is included as a part of the distribution. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2008-11-25 12:22:09
|
Revision: 13334 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13334&view=rev Author: pdontthink Date: 2008-11-25 11:33:00 +0000 (Tue, 25 Nov 2008) Log Message: ----------- Add configtest section and link to new untranslated special folders section in translator manual Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2008-11-25 11:27:20 UTC (rev 13333) +++ trunk/documentation/admin/admin.sgml 2008-11-25 11:33:00 UTC (rev 13334) @@ -2447,7 +2447,26 @@ <sect>Solving problems <sect1>Configtest <p> -Using configtest.php as a first diagnose tool. +When attempting to diagnose any issues with SquirrelMail, the first thing +to do is load up http://example.org/squirrelmail/src/configtest.php and ensure +that SquirrelMail can't already tell you what the problem is. + +Note that as of SquirrelMail version 1.5.2, you cannot view this page from +any computer other than the one where SquirrelMail is installed unless you +have enabled remote computers to view it by using the SquirrelMail +configuration tool (config/conf.pl, which is usually aliased to "configure" +in the main SquirrelMail directory) and going to "11. Tweaks" and then chossing +"7. Allow remote configtest". You can also edit the <tt/$allow_remote_configtest/ +setting directly in <tt>config/config.php</tt> if you prefer. Before leaving +this enabled, consider that exposing the kind of information it displays can +be a security concern, so you are advised to turn it off except when +specifically needed. + +Aside from diagnosing certain problems directly, this tool will also display +many pieces of information that may be very helpful when asking others to +help you with problems you cannot fix yourself. Therefore, this should always +be your first stop when any problems come up. + <sect1>Common PHP error messages <sect2>unknown function session_id() call <p> @@ -2620,6 +2639,10 @@ Folder Options. <sect1>Common interface error messages +<sect2>Special folders (Sent/Drafts/Trash) are not translated +<p> +See <url url="http://squirrelmail.org/docs/translator/translator-3.html#ss3.6" name="http://squirrelmail.org/docs/translator/translator-3.html#ss3.6"> + <sect2>Unknown username or password <p> password is not ********. you need cookies. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2008-12-04 00:26:18
|
Revision: 13337 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13337&view=rev Author: pdontthink Date: 2008-12-04 00:26:14 +0000 (Thu, 04 Dec 2008) Log Message: ----------- configtest is good to include in support requests Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2008-11-26 02:56:42 UTC (rev 13336) +++ trunk/documentation/admin/admin.sgml 2008-12-04 00:26:14 UTC (rev 13337) @@ -2757,8 +2757,10 @@ </itemize> The bug report plugin (bundled with SquirrelMail) collects a number of useful -details. Make sure that the data provided by it is part of your request for -support. +details, as does the +<tt>http://your-server/path-to-squirrelmail/src/configtest.php</tt> script +script. Make sure that the data provided by at least one of these is part of +your request for support. Read more about how to ask for support in a smart way at <url url="http://www.catb.org/~esr/faqs/smart-questions.html" name="How to Ask This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2008-12-28 23:26:21
|
Revision: 13385 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13385&view=rev Author: pdontthink Date: 2008-12-28 23:26:18 +0000 (Sun, 28 Dec 2008) Log Message: ----------- Update docs Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2008-12-23 03:04:17 UTC (rev 13384) +++ trunk/documentation/admin/admin.sgml 2008-12-28 23:26:18 UTC (rev 13385) @@ -1425,16 +1425,21 @@ <p> SquirrelMail is designed to work with one IMAP server. If you want to use the same SquirrelMail installation with multiple IMAP servers, you should be able to -implement this with Perdition mail proxy, or with the Vlogin or Multilogin plugins, -or write your own custom server mapping function. These tools allow users to -be transparently redirected to their correct mail servers. +implement this with Perdition mail proxy, with the Login Manager (vlogin) or +Multilogin plugins, or by writing your own custom server mapping function. These +tools allow users to be transparently redirected to their correct mail servers. +In the future, SquirrelMail will natively provide users with the ability to +check mail on multiple IMAP servers during one login session (some plumbing +for this feature has been added for this into version 1.5.2, but full support +is not yet implemented). + <sect2>Perdition proxy <p> <url url="http://www.vergenet.net/linux/perdition/" name="Perdition"> is POP and IMAP proxy server, that can redirect users to appropriate mail servers. -<sect2>Vlogin plugin +<sect2>Login Manager (vlogin) plugin <p> Found in the main SquirrelMail plugins repository, this plugin helps manage and manipulate usernames given at login time, and allows the use of different @@ -1448,17 +1453,19 @@ <sect2>sqimap_get_user_server <p> -SquirrelMail can use mapping by a user defined function -instead of IMAP server's address. If IMAP server's address is set to -<tt/map:some_function_name/, SquirrelMail functions should use provided username -as first function argument and replace mapping with address returned by -function. +SquirrelMail can use a custom mapping provided by a user-defined function +instead of the IMAP server address in the main configuration file. If the +IMAP server address is set to <tt/map:some_function_name/, SquirrelMail +will call that function (e.g., "some_function_name") to determine what IMAP +server address to use, passing the username as the first argument. The +function is expected to return the IMAP server address for that username. -SquirrelMail provides example <tt>map_yp_alias</tt> function that uses ypmatch -program to get IMAP servers from yellowpages (NIS). +SquirrelMail provides an example function called <tt>map_yp_alias</tt> that +uses the ypmatch program to get the IMAP server address from NIS (Yellow +Pages). -This feature is experimental. If some code does not take into account use of -mapping in imap server's address configuration, it might be broken. +This feature is experimental. If code somewhere in SquirrelMail or in a plugin +does not take into account the use of this custom mapping, it will break. <sect>Optimizing SquirrelMail<label id="optimization"> <p> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2009-03-27 07:14:08
|
Revision: 13482 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13482&view=rev Author: pdontthink Date: 2009-03-27 07:13:56 +0000 (Fri, 27 Mar 2009) Log Message: ----------- Update the upgrade section, synchronized with the doc/UPGRADE document in the stable and devel code branches. If you make changes to that section in the future, please remember to also update those to documents as well. Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-03-27 04:28:36 UTC (rev 13481) +++ trunk/documentation/admin/admin.sgml 2009-03-27 07:13:56 UTC (rev 13482) @@ -811,180 +811,337 @@ <sect>Upgrading SquirrelMail <p> -This chapter talks about upgrading an existing SquirrelMail install. +This chapter discusses upgrading an existing SquirrelMail installation. -<sect1>Backup old install +<sect1>Check requirements <p> -Make a backup of your current SquirrelMail directory. If you use "cp", be -sure to use the "-Rp" options. -R means recursive, and -p will save the -permissions in the directory. +The system requirements may have been changed between your previous +version and this version of SquirrelMail. The requirements won't change +(much) between stable releases but may change significantly between +different series (e.g. between 1.2.x and 1.4.x). Most notably, you need +at least PHP version 4.1.0. The <tt/ReleaseNotes/ file is a good source for +information about changed requirements. -In this example, we assume that your httpd document directory is -<tt>/home/httpd/html</tt>, that your SquirrelMail install is located at -<tt>/home/httpd/html/squirrelmail-1.0.6</tt>, and that your new SquirrelMail -version is 1.2.0. Substitute version numbers and names as required. +Also make sure to review the last section in this guide that details +some issues that can arise if you are upgrading to or from certain +versions. -<verb> -$ cd /home/httpd/html -$ cp -Rp squirrelmail-1.0.6 squirrelmail-1.0.6.bak -</verb> +<sect1>What to do with your old installation +<p> +Until you get your new version working right, you'll want to keep your +current version in place - you don't need to change it at all unless +you want to change its directory name to something like "<tt/squirrelmail-old/" +to reduce confusion (in Linux-like environments, use a command like +"<tt>mv squirrelmail-1.4.8 squirrelmail-old</tt>"). +In this guide, we'll assume your current version is installed in +<tt>/usr/share/squirrelmail-1.4.8</tt> and that you'll be leaving it unchanged +(until the upgrade is complete). + <sect1>Unpack new SquirrelMail <p> -Make sure that you are in your httpd document directory (<tt>/home/httpd/html</tt>) -and then unpack the SquirrelMail archive (whatever the filename is): +Make sure that you are in the directory that contains your SquirrelMail +installation (in our exmaple, <tt>/usr/share/</tt>) and then unarchive the new +SquirrelMail version you just downloaded (in our example, we'll assume +you downloaded the <tt>squirrelmail-1.4.17.tar.gz</tt> distribution package; +unpacking any other package is very similar). In a Linux-like environment, +that would look like this: + <verb> -$ tar -zxvf squirrelmail-1.2.0.tar.gz + $ cd /usr/share/ + $ tar zxvf squirrelmail-1.4.17.tar.gz </verb> -<sect1>Copy important files from old install +Of course, this assumes you placed the new version you downloaded into the +<tt>/usr/share/</tt> directory before you executed these commands. You should now +have a new directory called "<tt>squirrelmail-1.4.17</tt>" right next to your old +one (in this example "<tt>squirrelmail-1.4.8</tt>"). + +<sect1>Copy important files from old installation <p> The important files to copy are: <itemize> - <item>Preferences - <item>Config details + <item>Configuration files <item>Plugins + <item>Skins + <item>Translations <item>Themes (if you've edited or added any of them) + <item>Preferences (but only if you keep them inside the SquirrelMail directory) </itemize> -<sect2>Preferences +<sect2>Configuration files <p> -First, copy your preference data over to the new directory. Usually -this is ok, but if you are upgrading from anything less than 1.0.5, we -strongly suggest you let your users reset their preferences. There -were important security upgrades in 1.0.5 regarding preference files. +If at all possible, start the configuration process from scratch. This +way, you are much less prone to miss new configuration options or transfer +any incompatible settings from one version to the next. That said, when +upgrading between minor versions (e.g., within the 1.4 release series as +in this example), copying your configuration files from the old installation +to the new one should be perfectly acceptable. If you do so, it would be +a good idea to run the configuration utility once as well as view the +configuration test page to make sure that everything is OK. + +Again, we'll start from the directory that contains your SquirrelMail +installation(s), and these commands apply to Linux-like environments. + <verb> -$ cp squirrelmail-1.0.6.bak/data/* squirrelmail-1.2.0/data + $ cd /usr/share/ + $ cp -p squirrelmail-1.4.8/config/config.php squirrelmail-1.4.17/config/ </verb> -<sect2>Config details +If you have a local configuration file, copy that too: + +<verb> + $ cp -p squirrelmail-1.4.8/config/config_local.php squirrelmail-1.4.17/config/ +</verb> + +As of version 1.5.2, you could copy the file <tt/plugin_hooks.php/ too, but +since this file is automatically generated, it is much better to run the +configuration utility once, save your settings and let SquirrelMail +create that file for you. + +<sect2>Plugins <p> -If at all possible, start the configuration process from scratch. It is -much less prone to missing configuration options than copying your old -configuration. Ideally, you should just run conf.pl to reconfigure -SquirrelMail. If you decide to copy your old config.php over, we strongly -recommend that you run conf.pl to make sure things are correct and then save -the config file. +Like SquirrelMail, plugins are frequently updated with feature and security +improvements as well as to make them compatible with new SquirrelMail +releases. It is suggested that you download new versions of your plugins at +the same time you download your SquirrelMail installation, and that you +install your plugins fresh (it's easy, don't panic!). + +PLEASE NOTE: You should not try to replace plugins that are already included +in the SquirrelMail package. Sometimes third party plugins are brought into +the SquirrelMail core, so take a peek at your new installation's plugins +directory to see what is already there. You only need to download or copy +your previous installation of third party plugins that are not in your new +SquirrelMail package by default. + +If you decide to copy plugin installations from your old installation, you +can copy an entire plugin directory from the old installation to the new +one (this example uses the Email Footer plugin): + <verb> -$ cp squirrelmail-1.0.6.bak/config/config.php squirrelmail-1.2.0/config + $ cp -Rp squirrelmail-1.4.8/plugins/email_footer squirrelmail-1.4.17/plugins/ </verb> -<sect2>Copy plugins +If you have configured any plugins so that their configuration files are +stored in the main SquirrelMail <tt>config/</tt> directory, you'll want to copy +those files, too. Again, using the Email Footer example: + +<verb> + $ cp -p squirrelmail-1.4.8/config/config_email_footer.php squirrelmail-1.4.17/config/ +</verb> + +<sect2>Skins <p> -Like SquirrelMail, plugins are frequently updated for improvements, as well -as to make them compatible with new SquirrelMail releases. It is suggested -that you download new versions of your plugins at the same time you download -your SquirrelMail install, and that you install your plugins fresh (it's -easy, don't panic!). +Skins (template sets) are handled the same as plugins are (and are only +part of SquirrelMail versions 1.5.2 and up). As skins are updated regularly, +it's always best to just download and install the newest versions of your +skins when you download your SquirrelMail upgrade package. -You should not try replacing plugins that are already included in the SquirrelMail -package. Download latest versions of plugins that are not included in the new -SquirrelMail package or copy them from your older SquirrelMail install. +PLEASE NOTE: As with plugins, you should not try to replace skins that are +already included in the SquirrelMail package. You only need to download or +copy your previous installation of third party skins that are not in your +new SquirrelMail package by default. -<sect2>Copy themes +If you decide to copy skin installations from your old installation, you +can copy an entire skin/template directory from the old installation to the +new one (this example uses the Default Smarty skin pack): + +<verb> + $ cp -Rp squirrelmail-1.5.2/templates/default_smarty squirrelmail-1.5.3/templates/ +</verb> + +<sect2>Translations <p> -TODO: this changes in 1.5.2 +Here again, we recommend that you simply download and install your +desired language translations from the newest locales pack on the +SquirrelMail website. If, however, you want to copy what you had +before, it's easiest to simply move the <tt>locale/</tt> directory in the new +installation out of the way and copy the old one into its place: +<verb> + $ mv squirrelmail-1.4.17/locale/ squirrelmail-1.4.17/locale-new + $ cp -Rp squirrelmail-1.4.8/locale/ squirrelmail-1.4.17/ +</verb> + +<sect2>Themes +<p> If you've created or modified themes, you should copy just those to the new -SquirrelMail themes directory. To just copy them all over to the new -SquirrelMail installation, you can run one command. +SquirrelMail <tt>themes</tt> directory: + <verb> -$ cp -ui squirrelmail-1.0.6.bak/themes/* squirrelmail-1.2.0/themes/ + $ cp -pi squirrelmail-1.4.8/themes/* squirrelmail-1.4.17/themes/ </verb> -When <tt/-u/ flag is used, command copies only missing and newer files. -When <tt/-i/ flag is used, command will ask for confirmation before replacing -existing files. +<sect2>Preferences +<p> +Chances are that, as long as you followed our installation recommendations, +you don't need to make any changes for your user preferences. That is, +if you have preferences stored in a database or you have moved your +preference file storage outside the SquirrelMail directory (such as +<tt>/var/lib/squirrelmail/data/</tt>) as explained in our installation documents, +then you don't need to do anything. -If you want to see your theme in future SquirrelMail packages, send it to -SquirrelMail developers. They might add it to the themes in the standard -install! +However, note that when upgrading between major versions (such as between +1.4.x and 1.5.x), it is usually best to create a secondary preferences +storage location and start with a fresh system for your users to configure. +That said, many preferences are the same between versions and to date there +are no known incompatibilities between 1.4.x preferences and 1.5.x preferences. -<sect1>Change permissions -<p> -The web server must have write permission to the data directory. In this -example, we assume that user "nobody" and group "nobody" are the web server -as is often the case with Apache. +If you have your preferences stored inside your old SquirrelMail +installation, we'd STRONGLY encourage you to re-read our installation +information and consider moving them away from the web server's reach. +If for some reason you need to continue to store your preferences inside +the SquirrelMail installation, you can move the new <tt>data/</tt> directory out +of the way and copy the old preferences to the new installation: + <verb> - $ cd squirrelmail-1.2.0 - $ chown -R nobody:nobody data + $ mv squirrelmail-1.4.17/data/ squirrelmail-1.4.17/data-new + $ cp -Rp squirrelmail-1.4.8/data/ squirrelmail-1.4.17/ </verb> -Check your webserver's configuration file. It might be using different -userid/groupid pair. Additionally, if "chown user:group" doesn't work, you can -use "chown user" and "chgrp group" instead. See the man pages for these commands -for more information. +If you are using Windows or otherwise cannot use the commands above, please +make sure that you preserve the permissions and ownership of the <tt>data/</tt> +directory as you move it, since SquirrelMail will not work unless the web +server has write permission in the data directory (which, presumably, your +old data directory has been set up with). -If you are using SquirrelMail in setup with PHP <tt/safe_mode/ restrictions, -data and attachment directories should be owned by same user that owns other -SquirrelMail scripts. It must be writable by the web server group (see <ref -id="safe_mode" name="Safe mode">). +PLEASE NOTE: If you are upgrading from versions lower than 1.0.5, you +are STRONGLY encouraged NOT to migrate preferences, since there were +important security upgrades in the preferences system starting with +SquirrelMail version 1.0.5. -<sect1>Run conf.pl +<sect1>Run the configuration utility <p> -Run config/conf.pl to see the new configuration options available with the -new version, as well as to verify that all of your old options are set -properly. +Although not strictly necessary for minor upgrades, we STRONGLY +recommend that you run <tt>config/conf.pl</tt> to see the new +configuration options available with the new version, as well as +to verify that all of your old options are set properly. In SquirrelMail +versions 1.5.2 and above, this also ensures that your plugins are +properly registered with SquirrelMail. -Always save your options, also if you haven't changed anything. -This will ensure that any problems with conf.pl that might have been solved -are effective to your installation. +Always save your options, even if you haven't changed anything. This +will ensure that any problems with your configuration that have been +automatically detected and fixed are not lost. -If you want to make sure that your configuration contains all themes included in -new SquirrelMail package, go to theme options in configuration utility and -run theme detection command. +If you want to make sure that your configuration contains all themes +included in new SquirrelMail package, go to theme options in +configuration utility and run theme detection command. -<sect1>Version specific notes -<sect2>Upgrade from version older than 1.2.2 to later version. +<sect1>Visit src/configtest.php <p> -In order to provide better internationalization support, developers have changed -names used by translations. From 1.2.2 SquirrelMail uses language and country -codes in translation names. In most of cases upgraded SquirrelMail should work -correctly. Only Norwegian Nynorsk (no_NO_ny) translation might need fixes. If -your user preference files contain <tt/language=no_NO_ny/ lines, these lines -should be updated to <tt/language=nn_NO/. +You should browse to <tt>http://example.com/squirrelmail/src/configtest.php</tt> +(adjust the address to suit your system) and confirm that there are no +configuration problems. Note that in versions 1.5.0 and up, you'll need +to make sure <tt>$allow_remote_configtest</tt> is enabled in your configuration +file to do so (or see "<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" in +the configuration utility). -<sect2>Upgrade from 1.2.x or older versions to 1.4.x or later. +<sect1>Verify that the new installation works <p> -Layout changes. Plugins can break. +Log in and take a look around in your new installation and make sure +everything is working as expected. -<sect2>Upgrade from version older than 1.4.4 to later version. +<sect1>Follow-up <p> -Translations are removed in order to reduce package size. You must download -and install separate translation packages. +Once you've finished upgrading, you may want to keep an archived copy +of your old installation just in case something goes wrong with the new +one. You can simply move the whole directory somewhere else outside +of your web server's document root or compress the directory into an +archive file for storage elsewhere. Here's how to create a zip file +of your old installation in a Linux-like environment: -<sect2>Downgrade from 1.5.1 to older version. -<p> -Index Order options are not preserved. +<verb> + $ cd /usr/share/ + $ zip -r squirrelmail-1.4.8.zip squirrelmail-1.4.8 +</verb> -SquirrelSpell user dictionaries are not preserved. +Or to create a gzipped tar archive: -<sect1>Recheck new install -<p> -Login into new SquirrelMail install and check if everything is working. +<verb> + $ tar czvf squirrelmail-1.4.8.tar.gz squirrelmail-1.4.8 +</verb> -<sect1>Replace old install. +Then make sure that you REMOVE the old directory so users can no longer +access it - if you don't do this, you may be leaving yourself exposed +to known security exploits. + +<sect1>How to point the web server to different SquirrelMail installations <p> -Redirect your users to new SquirrelMail install. You can use Apache <url -url="http://httpd.apache.org/docs/mod/mod_alias.html#redirectperm" -name="RedirectPermanent"> directive or other redirection tools provided by your -webserver. +In this guide, we assumed that your installation directories looked +like "<tt>squirrelmail-1.4.17</tt>". Most of the time, you'll want to allow +your users to type in "<tt>squirrelmail</tt>" (or just "<tt>webmail</tt>" or "<tt>mail</tt>") +without needing to know the version number. Of course, you can simply +change the name of the SquirrelMail installation directory: -If you use SquirrelMail directory without version information, you can also -replace it with new SquirrelMail directory. <verb> -$ mv /home/httpd/html/squirrelmail /home/httpd/html/squirrelmail.old -$ mv /home/httpd/html/squirrelmail.new /home/httpd/html/squirrelmail + $ cd /usr/share/ + $ mv squirrelmail-1.4.8 mail </verb> -<sect1>DONE! +... but there are several more graceful ways you can achieve this. +In any Linux-like system, you can use symlinks to dynamically point +"webmail" to any of your version-specific installations: + +<verb> + $ cd /usr/share/ + $ ln -s squirrelmail-1.4.8 mail +</verb> + +Note that symlinks can point anywhere you need them to, so the installation +directory doesn't necessarily need to be in the same place the "<tt>mail</tt>" link +is. + +You can also configure most any web server to point to your installation +directory from any incoming address you desire. There are several +redirection and address re-writing tools for most web servers, so this is +just one example using Apache's Redirect directive: + +<verb> + Redirect permanent /squirrelmail-1.4.17 https://example.com/mail +</verb> + +<sect1>Version-specific upgrade issues + +<sect2>Upgrading from the 1.4 release series to the 1.5 release series <p> -That should be all! The most important part is copying your users' -preference files back into the new data directory. This will insure that -your users will have their old preferences. Remember to do so with caution, -especially if you are upgrading from a version before 1.0.5 to version 1.0.5 -or later. +The plugin API changed substantially in version 1.5.2. At the least, +you should NOT copy your old plugins when making this kind of upgrade. +<sect2>Upgrading from the 1.2 release series to the 1.4 release series +<p> +Several layout changes were made and there were other changes that require +plugin updates. At the least, you should NOT copy your old plugins when +making this kind of upgrade. + +<sect2>Upgrading from any version older than 1.4.4 to version 1.4.4 or later +<p> +Translations were removed from the main SquirrelMail package. Unless +you copy the translations from your old installation, you will now need +to visit the SquirrelMail download page and also get a copy of the our +locales package. + +<sect2>Downgrading from version 1.5.1 to any version older than 1.5.1 +<p> +The "<tt>Index Order</tt>" options and SquirrelSpell user dictionaries will not be +preserved if you use the same user preferences, although we discourage the +use of the same preference sets between major release numbers (e.g., 1.4.x +and 1.5.x). + +<sect2>Upgrading from any version older than 1.2.2 to version 1.2.2 or later +<p> +The names used by some translations were changed starting in version 1.2.2. +In most cases, you won't see any problems due to this change, however, +the Norwegian Nynorsk (<tt>no_NO_ny</tt>) translation might need to be fixed. If +you decide to retain the same preferences from your old installation, any +users who have a "<tt>language</tt>" preference set to "<tt>no_NO_ny</tt>" will need to +have it manually changed to "<tt>nn_NO</tt>". + +<sect2>Upgrading from any version older than 1.0.5 to version 1.0.5 or later +<p> +Some important security upgrades were made to the preferences system +in version 1.0.5. It is NOT recommended that you retain user preferences +when upgrading from versions older than 1.0.5. + <sect>Configuring SquirrelMail<label id="configuring"> <p> Even though the size of this documentation might indicate otherwise, This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2009-03-29 01:11:49
|
Revision: 13489 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13489&view=rev Author: pdontthink Date: 2009-03-29 01:11:42 +0000 (Sun, 29 Mar 2009) Log Message: ----------- Bunch of fixes and new info, mainly for the installation sections Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-03-29 00:13:34 UTC (rev 13488) +++ trunk/documentation/admin/admin.sgml 2009-03-29 01:11:42 UTC (rev 13489) @@ -359,89 +359,164 @@ <sect2>Download all required software <p> -You can find SquirrelMail package on <url url="http://squirrelmail.org" -name="SquirrelMail site">. PHP can be found on <url url="http://php.net" +You can find the SquirrelMail package at the <url url="http://squirrelmail.org" +name="SquirrelMail site">. PHP can be found at the <url url="http://php.net" name="PHP site">. -<sect2>Install webserver and PHP (at least 4.1.0). +<sect2>Install web server and PHP (version 4.1.0 or above) <p> -SquirrelMail needs a webserver with PHP support. Check <url -url="http://php.net/manual/en/install.php" name="PHP install manual"> for -information about supported web servers and install procedures. +SquirrelMail needs a web server with PHP support. Please refere to the <url +url="http://php.net/manual/en/install.php" name="PHP installation manual"> +for information about what web servers PHP works with and its installation +procedures. -Some Linux and Unix distributions provide precompiled web server and php packages. +Note that some Linux and Unix distributions provide a precompiled web server +with PHP support built in. We recommend the following PHP settings: <itemize> - <item><tt/register_globals/ off - a dangerous setting, not needed. We do - not release security advisories for issues only exploitable with this - setting on. Note that you can easily enable it only for some legacy - site that may need it and turn it off globally. - <item><tt/magic_quotes_{runtime,gpc,sybase}/ off - SquirrelMail may work - with any of these on, but if you experience stray backslashes in your - mail or other strange behaviour, it may be advisable to turn them off. - <item><tt/file_uploads/ on - needed if your users want to attach files to - their mails. - <item><tt/safe_mode/ on or off - safe_mode on is only a tiny bint more - secure, in the SquirrelMail case. There may be some incompatibilities - with some functionality (see <ref id="safe_mode" name="Safe mode">). + <item><bf><tt>register_globals</tt> off</bf> - This is a dangerous setting + when enabled, and is not generally needed for most recent PHP + applications. We no longer release security advisories for issues only + exploitable with this setting turned on because it has long been a + well-known weakness in PHP (and has been removed from PHP 6). Note + that you can easily enable it only for a single legacy application + that may require it while keeping the default off for the rest of + your applications. + <item><bf><tt>magic_quotes_{runtime, gpc, sybase}</tt> off</bf> - SquirrelMail + may work with any of these turned on, but if you experience stray + backslashes in your mail or other strange behaviour, it may be advisable + to turn them off. + <item><bf><tt>file_uploads</tt> on</bf> - This is needed if your users want + to attach files to their emails. + <item><bf><tt>safe_mode</tt> on or off</bf> - Turning safe mode on in + SquirrelMail's case is not much more secure than having it off. + When it is enabled, incompatibilities with some functionality + may arise (see our <ref id="safe_mode" name="safe mode notes">). </itemize> <sect2>Install IMAP server <p> -It depends on used email system. Email server needs IMAP service that knows -used email system layout. If you use Unix with standard sendmail server, you -might have to install UW IMAP, Dovecot or other IMAP server, that can use email -stored in /var/spool/mail/ directory. If you use Windows, you might have to -enable IMAP service that is bundled with your email server. If your email server -does not support IMAP, you might have to find some other email server product. +What IMAP server you can use depends on what the other components in your +email system are and how they were installed and configured. The IMAP server +needs to understand and be compatible with how messages are stored on your +system. +If you use Unix or Linux with a standard sendmail <url +url="http://wikipedia.org/wiki/Mail_transfer_agent" name="MTA"> server, you +probably have to install an IMAP server that works with mail stored in +<tt>/var/spool/mail/</tt>, such as UW IMAP, Dovecot, etc. + +If you are running your email server on a Windows platform, you might have to +enable an IMAP service that is bundled with your email server. + +If your email server does not support IMAP, you might have to find some other +email server product. + <sect2>Unpack SquirrelMail package <p> Unpack the SquirrelMail package in a web-accessible location. <sect2>Prepare data and attachment directories <p> -Select a data-dir and attachment dir, outside the webtree (e.g. in /var). -The data-dir (for user prefs) should be owned by the user the webserver -runs as (e.g. www-data). The attachment dir (for uploading files as -attachments) should be file mode 0730 and in the same group as the -webserver. +Select a data dirrectory and attachment dirrectory outside of the web +server's reach (for example in a Unix or Linux environment, a subdirectory +of /var is a good place for these). -If you use PHP with safe mode enabled, check chapter about safe mode. +The data directory is where SquirrelMail user preferences are stored - even +when you have configured SquirrelMail to store user preferences in a database, +some plugins might still need to use this directory. The attachment directory +is used mainly for temporary storage of file uploads that will become email +attachments. +Both of these directories should be writable (not readable) by the web server +and no one else (except you). In a Unix or Linux environment, that means that +they should be owned by the root user if possible (otherwise whatever user you +log in as), their group should be the same as that that the web server runs as +(e.g. "www-data", "apache", "nobody", "wheel", etc.), and their permissions +should be 0730 (rwx-wx---). + +If you use PHP with safe mode enabled, check our <ref id="safe_mode" +name="safe mode notes"> which explain other possible limitations on these +directories. + +<sect2>Directory access considerations +<p> +Only a small subset of the SquirrelMail source code needs to be directly +accessible to users' browsers. The rest of the source code is used internally +by SquirrelMail. Leaving the entire source tree open to outside access is +not a problem or vulnerability, but some attackers have been known to snoop +for old versions of SquirrelMail by trying to inspect things such as the +ChangeLog file. If you want to employ the maximum level of protection against +snoops and would-be attackers, you can make use of the .htaccess files that +come with the SquirrelMail source code by adding +"<tt>AllowOverride AuthConfig</tt>" to the <tt>Directory</tt> settings for +SquirrelMail in your Apache configuration file (if using the Apache web server), +or you can use the <tt>Directory</tt> settings suggested in the +<ref id="apache_configuration" name="apache configuration"> section below. + <sect2>Configure SquirrelMail <p> -Run <tt>config/conf.pl</tt> from the command line. Use the D option to load -predefined options for specific IMAP servers, and edit at least the -Server Settings and General Options (datadir). +Run <tt>config/conf.pl</tt> (or just <tt>configure</tt>) from the command +line. This is a Perl script, so if you do not have Perl installed, please +refer to our notes about <ref id="configuration_without_shell_access" +name="how to configure SquirrelMail without shell access">. +Use the D option to load predefined settings for your particular IMAP server, +and edit at least the Server Settings and General Options (making sure to set +the "Data Directory" and "Attachment Directory" settings). + <sect2>Check your SquirrelMail configuration <p> -Browse to http://example.com/yourwebmaillocation/src/configtest.php -to test your configuration for common errors. +Browse to http://example.com/squirrelmail/src/configtest.php +to test your configuration for common errors. You'll need to adjust the +"squirrelmail" part to match the location where you installed it. Note that +in SquirrelMail versions 1.5.0 and up, if you are accessing configtest.php +from any place other than the machine where SquirrelMail is installed, you'll +need to make sure <tt>$allow_remote_configtest</tt> is enabled in your +configuration file to do so (or see "<tt>11. Tweaks</tt>" ==> +"<tt>7. Allow remote configtest</tt>" in the configuration utility). If you +do that, be sure to disable it again when you are finished. <sect2>Log into SquirrelMail <p> -Browse to http://example.com/yourwebmaillocation/ to log in. +Browse to http://example.com/squirrelmail/ to log in. Again, you'll need to +change "squirrelmail" to whatever the location is that you have it installed. <sect1>Installing SquirrelMail on Unix and Linux systems <p> -This chapter covers installation of SquirrelMail on generic Unix or Linux -system. It does not cover installation of operating system or tools required to -install web server or PHP. +This chapter covers the installation of SquirrelMail and related packages on +a generic Unix or Linux system. It does not cover the installation of the +operating system or any other tools required for a fully functional email +system. -Any version numbers used in examples are specific to the time when this -documentation is written. If current version numbers differ, make sure that you -are not using old, obsolete or vulnerable software. +Any version numbers used in these examples are specific to the time when this +documentation was written. You should generally use the most up to date +versions of all software involved. That is, if there are newer versions of +these packages available now, you'll probably want to substitute the newer +numbers in the examples below. Make sure that you are not using old, obsolete +or vulnerable software! -Guide uses UW IMAP server as example. This IMAP server can be used in generic -email setup when incoming mail is stored in <tt>/var/spool/mail</tt> -directory. If you are planning to use webmail with big number of users or with -bigger mailboxes, consider using different IMAP server and redesign entire email -system. +This guide uses the UW IMAP server, because it is a simple (and ubiquitous) +example and because it can be used in most generic email system setups where +incoming mail is stored in the <tt>/var/spool/mail</tt> directory. If you are +planning to offer webmail on a system with a large number of users or where +users have large mailboxes, consider planning a better email system design +and using different IMAP server software. +PLEASE NOTE that before you begin installing such things as a web server, PHP +or an IMAP server, you should check whether or not your system already has +such software installed. Many server-class systems come with that kind of +software ready to go. Also note that these installation instructions use +generic compilation commands that should work on most any system, however your +system may have more graceful (and even easier) ways to install software, +like the <tt>apt-get</tt> tool in systems such as Debian and the <tt>yum</tt> +tool in systems such as Fedora/Red Hat. + +Typically, you'll need to have root-level access to your server to perform +these operations. + <sect2>Download required software <p> You will need: @@ -459,90 +534,111 @@ <tscreen><verb> # install -d /usr/local/src/downloads # cd /usr/local/src/downloads -# wget http://some-apache-mirror-server/apache/httpd/httpd-2.0.54.tar.gz -# wget http://some-php-mirror-server/get/php-4.3.11.tar.bz2/from/this/mirror +# wget http://some-apache-mirror-server/apache/httpd/httpd-2.2.11.tar.gz +# wget http://www.php.net/get/php-5.2.9.tar.bz2/from/a/mirror # wget ftp://ftp.cac.washington.edu/mail/imap.tar.Z -# wget http://some-sourceforge-mirror/some-path/squirrelmail-1.4.5.tar.bz2 +# wget http://some-sourceforge-mirror/some-path/squirrelmail-1.4.17.tar.bz2 </verb></tscreen> -<sect2>Unpack and install apache +<sect2>Unpack and install Apache <p> <tscreen><verb> # cd /usr/local/src -# tar -xzvf /usr/local/src/downloads/httpd-2.0.54.tar.gz -# cd httpd-2.0.54 +# tar -xzvf /usr/local/src/downloads/httpd-2.2.11.tar.gz +# cd httpd-2.2.11 # ./configure --prefix=/usr/local/apache --enable-module=so # make # make install </verb></tscreen> -<sect2>Unpack and install php +<sect2>Unpack and install PHP <p> <tscreen><verb> # cd /usr/local/src -# tar --bzip2 -xvf /usr/local/src/downloads/php-4.3.11.tar.bz2 -# cd php-4.3.11 +# tar --bzip2 -xvf /usr/local/src/downloads/php-5.2.9.tar.bz2 +# cd php-5.2.9 # ./configure --prefix=/usr/local/php \ > --with-apxs2=/usr/local/apache/bin/apxs # make # make install </verb></tscreen> -If you configure PHP compilation with <tt/--disable-all/ option, you must add -<tt/--enable-session/ and <tt/--with-pcre-regex/ options. +Note that if you decide to configure your PHP compilation with the +<tt/--disable-all/ option, you must also add the <tt/--enable-session/ and +<tt/--with-pcre-regex/ options. -<sect2>Add PHP support to apache +<sect2>Add PHP support to Apache <p> +In your main Apache configuration file (typically +<tt>/etc/httpd/conf/httpd.conf</tt>), add this: + <tscreen><verb> -<IfModule mod_php4.c> +<IfModule mod_php5.c> AddType application/x-httpd-php .php </IfModule> </verb></tscreen> -<sect2>Restart apache and check if php is working +<sect2>Restart Apache and check if PHP is working <p> +Execute the restart request from the command line: + <tscreen><verb> -/usr/local/apache/bin/apachectl graceful +# /usr/local/apache/bin/apachectl graceful </verb></tscreen> +Create a test file in the document root of Apache and put this in it: + <tscreen><verb> <?php phpinfo(); ?> </verb></tscreen> -<sect2>Unpack and install imap server +Load that file in a web browser and make sure it displays a page describing +your PHP system details. + +<sect2>Unpack and install IMAP server <p> -Unpack UW IMAP archive. +Unpack the UW IMAP package. + <tscreen><verb> # cd /usr/local/src # tar -xzvf /usr/local/src/downloads/imap.tar.Z </verb></tscreen> -Compile UW IMAP +Compile UW IMAP: + <tscreen><verb> -cd /usr/local/src/imap-<someversion> -make port-name EXTRADRIVERS='' SSLTYPE=unix +# cd /usr/local/src/imap-<some version> +# make port-name EXTRADRIVERS='' SSLTYPE=unix </verb></tscreen> -Replace <tt>port-name</tt> with name that matches your system. Check Makefile -for possible values. If you haven't installed OpenSSL libraries and headers, use -<tt>SSLTYPE=none</tt> instead of <tt>SSLTYPE=unix</tt>. +Replace "<tt>port-name</tt>" above with the name that matches your system. +Check the file "<tt>Makefile</tt>" for possible values. If you haven't +installed OpenSSL libraries and headers, use "<tt>SSLTYPE=none</tt>" instead +of "<tt>SSLTYPE=unix</tt>". -Install IMAP server binary +Install IMAP server binary: + <tscreen><verb> -strip imapd/imapd -install -d /usr/local/libexec/ -cp imapd/imapd /usr/local/libexec/ +# strip imapd/imapd +# install -d /usr/local/libexec/ +# cp imapd/imapd /usr/local/libexec/ </verb></tscreen> -Enable IMAP server in inetd.conf +Enable IMAP server in <tt>inetd.conf</tt>: + <tscreen><verb> imap2 stream tcp nowait root /usr/sbin/tcpd /usr/local/libexec/imapd </verb></tscreen> -Restart inetd +Now, restart inetd. <sect2>Prepare SquirrelMail directories <p> +Make sure to change "nogroup" to whatever group Apache will be running as. +You can check what that is by looking at the value of the "Group" setting +in your Apache main configuration file (probably +<tt>/etc/httpd/conf/httpd.conf</tt>). + <tscreen><verb> # mkdir /usr/local/squirrelmail # cd /usr/local/squirrelmail @@ -555,40 +651,96 @@ <p> <tscreen><verb> # cd /usr/local/squirrelmail -# tar --bzip2 -xvf /usr/local/src/downloads/squirrelmail-1.4.5.tar.bz2 -# mv squirrelmail-1.4.5 www +# tar --bzip2 -xvf /usr/local/src/downloads/squirrelmail-1.4.17.tar.bz2 +# mv squirrelmail-1.4.17 www </verb></tscreen> <sect2>Configure SquirrelMail <p> -Start SquirrelMail configuration utility. Configure SquirrelMail with UW -preset. Set data and attachment directories. +Run the SquirrelMail configuration utility. -<sect2>Configure access to SquirrelMail in Apache +<tscreen><verb> +# cd /usr/local/squirrelmail +# www/configure +</verb></tscreen> + +This is a Perl script, so if you do not have Perl installed, please refer +to our notes about <ref id="configuration_without_shell_access" +name="how to configure SquirrelMail without shell access">. + +Select the "D" option and then configure SquirrelMail with the "uw" preset. +Also make sure to set the data and attachment directory settings +("<tt>/usr/local/squirrelmail/data</tt>" and +"<tt>/usr/local/squirrelmail/temp</tt>" respectively) under +"<tt>4. General Options</tt>". Make any other changes as you see fit, +select "S" to save and then "Q" to quit. + +<sect2>Configure access to SquirrelMail in Apache<label id="apache_configuration"> <p> -Modify httpd.conf +Modify your main Apache configuration file (typically +<tt>/etc/httpd/conf/httpd.conf</tt>) by adding the following: <tscreen><verb> Alias /squirrelmail /usr/local/squirrelmail/www <Directory /usr/local/squirrelmail/www> - Options Indexes - AllowOverride none + Options None + AllowOverride None DirectoryIndex index.php - Order allow,deny - allow from all + Order Allow,Deny + Allow from all </Directory> +<Directory /usr/local/squirrelmail/www/*> + Deny from all +</Directory> +<Directory /usr/local/squirrelmail/www/images> + Allow from all +</Directory> +<Directory /usr/local/squirrelmail/www/plugins> + Allow from all +</Directory> +<Directory /usr/local/squirrelmail/www/src> + Allow from all +</Directory> +<Directory /usr/local/squirrelmail/www/templates> + Allow from all +</Directory> +<Directory /usr/local/squirrelmail/www/themes> + Allow from all +</Directory> +<Directory /usr/local/squirrelmail/www/contrib> + Order Deny,Allow + Deny from All + Allow from 127 + Allow from 10 + Allow from 192 +</Directory> +<Directory /usr/local/squirrelmail/www/doc> + Order Deny,Allow + Deny from All + Allow from 127 + Allow from 10 + Allow from 192 +</Directory> </verb></tscreen> +Now restart Apache from the command line: + +<tscreen><verb> +# /usr/local/apache/bin/apachectl graceful +</verb></tscreen> + +You also might be interested in <ref id="point_web_server_to_squirrelmail" +name="how to alias different locations to your SquirrelMail installation">. + <sect2>Log into SquirrelMail <p> -After you add alias to SquirrelMail in apache configuration and restart apache, -you should be able to access SquirrelMail by going to -<tt>http://your-server/squirrelmail</tt>. +Now you should be able to access SquirrelMail by going to +<tt>http://example.com/squirrelmail</tt>. <sect1>Installing SquirrelMail on a hosted service without shell access <p> -How to install SquirrelMail on a server where you do not have shell access or -administrative access. +This chapter discusses how to install SquirrelMail on a server where you do not +have shell access or administrative access. <sect2>Requirements <p> @@ -625,7 +777,7 @@ SquirrelMail is installed by copying all of its files to the web server. You should be able to do that with a FTP, SFTP or FTP-SSL client program. -<sect2>Configuration +<sect2>Configuration<label id="configuration_without_shell_access"> <p> You need to create a configuration file for SquirrelMail. If you have Perl on your own computer, you can run the SquirrelMail @@ -769,18 +921,29 @@ <p> After you have uploaded <tt>config.php</tt> to the SquirrelMail <tt>config/</tt> directory, go to -<tt>http://your-server/path-to-squirrelmail/src/configtest.php</tt> -and check if the configuration is correct so far. Every time you -change your configuration file, it is a good idea to re-visit -this page to make sure everything is working correctly. This -page includes making a test connection to the IMAP server, so +<tt>http://example.com/squirrelmail/src/configtest.php</tt> +and check if the configuration is correct so far. You'll need to +adjust the "squirrelmail" part to match the location where you +installed it. Note that in SquirrelMail versions 1.5.0 and up, +if you are accessing configtest.php +from any place other than the machine where SquirrelMail is installed, +you'll need to make sure <tt>$allow_remote_configtest</tt> is +enabled in your configuration file to do so (or see +"<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" in +the configuration utility). If you do that, be sure to disable it +again when you are finished. + +Every time you change your configuration file, it is a good idea +to re-visit this page to make sure everything is working correctly. +This page includes making a test connection to the IMAP server, so make sure it is working correctly and accepting connections. <sect2>First login <p> Go to -<tt>http://your-server/path-to-squirrelmail/src/login.php</tt> -and try logging in. You should use a user name and password that +<tt>http://example.com/squirrelmail/src/login.php</tt> and try logging +in. You'll need to adjust the "squirrelmail" part to match the location +where you installed it. You should use a user name and password that are known to work with your IMAP server. <sect1>Prepackaged SquirrelMail installs @@ -1031,10 +1194,13 @@ <p> You should browse to <tt>http://example.com/squirrelmail/src/configtest.php</tt> (adjust the address to suit your system) and confirm that there are no -configuration problems. Note that in versions 1.5.0 and up, you'll need -to make sure <tt>$allow_remote_configtest</tt> is enabled in your configuration -file to do so (or see "<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" in -the configuration utility). +configuration problems. Note that in versions 1.5.0 and up, if you are +accessing configtest.php from any place other than the machine where +SquirrelMail is installed, you'll need to make sure +<tt>$allow_remote_configtest</tt> is enabled in your configuration file to do so +(or see "<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" in +the configuration utility). If you do that, be sure to disable it again when +you are finished. <sect1>Verify that the new installation works <p> @@ -1066,16 +1232,17 @@ to known security exploits. <sect1>How to point the web server to different SquirrelMail installations +<label id="point_web_server_to_squirrelmail"> <p> In this guide, we assumed that your installation directories looked like "<tt>squirrelmail-1.4.17</tt>". Most of the time, you'll want to allow -your users to type in "<tt>squirrelmail</tt>" (or just "<tt>webmail</tt>" or "<tt>mail</tt>") -without needing to know the version number. Of course, you can simply -change the name of the SquirrelMail installation directory: +your users to type in "<tt>squirrelmail</tt>" (or just "<tt>webmail</tt>" +or "<tt>mail</tt>") without needing to know the version number. Of course, +you can simply change the name of the SquirrelMail installation directory: <verb> $ cd /usr/share/ - $ mv squirrelmail-1.4.8 mail + $ mv squirrelmail-1.4.17 mail </verb> ... but there are several more graceful ways you can achieve this. @@ -1084,7 +1251,7 @@ <verb> $ cd /usr/share/ - $ ln -s squirrelmail-1.4.8 mail + $ ln -s squirrelmail-1.4.17 mail </verb> Note that symlinks can point anywhere you need them to, so the installation @@ -2133,7 +2300,7 @@ SquirrelMail implements translations with gettext functions. Interface can use PHP gettext extension or internal gettext implementation. If PHP gettext -extension is used, it might require special webserver setup. On Linux gettext +extension is used, it might require a special web server setup. On Linux gettext functions work only when appropriate system locales are available. On BSD you should be able to set LC_ALL environment variable in PHP script. There are some differences between GNU Gettext and Solaris Gettext implementations. @@ -2262,8 +2429,8 @@ test|Testname|Testsurname|te...@ex...|testinfo </verb></tscreen> -4. If you want writable address book, file must be writable by webserver -user. +4. If you want a writable address book, the file must be writable by the user +that the web server runs as. 5. After you have created address book file, go to SquirrelMail configuration utility, select 6. Address Books option and configure address book in 3. @@ -2325,7 +2492,7 @@ SquirrelMail is webmail interface written in PHP. Webmail interface could be attacked through specifically crafted emails, interface programming mistakes and user information hijacking. It can be used to send unsolicited email -messages from hijacked or abused email account. +messages from a hijacked or abused email account. In order to prevent crafted email exploits SquirrelMail uses special <url url="http://linux.duke.edu/projects/mini/htmlfilter/" name="htmlfilter"> @@ -2337,7 +2504,7 @@ Interface programming mistakes usually can exploited only by authenticated user. They can lead to hijacking of other users' data or executing scripts with -webserver user privileges. SquirrelMail developers are trying to prevent such +web server user privileges. SquirrelMail developers are trying to prevent such exploits. If you find some way to security of SquirrelMail scripts, inform about it SquirrelMail developers. @@ -2423,7 +2590,7 @@ SquirrelMail secure_login and show_ssl_link plugins can be used to warn users about insecure connections and/or provide automatic redirection to a secured server. -In the Apache webserver, redirection can be implemented with Redirect directives and +In the Apache web server, redirection can be implemented with Redirect directives and the mod_rewrite module. For example: <tscreen><verb> @@ -2615,7 +2782,7 @@ to do is load up http://example.org/squirrelmail/src/configtest.php and ensure that SquirrelMail can't already tell you what the problem is. -Note that as of SquirrelMail version 1.5.2, you cannot view this page from +Note that as of SquirrelMail version 1.5.0, you cannot view this page from any computer other than the one where SquirrelMail is installed unless you have enabled remote computers to view it by using the SquirrelMail configuration tool (config/conf.pl, which is usually aliased to "configure" @@ -2725,10 +2892,10 @@ Default preference file (frequently named <tt/default_pref/) AND the default data directory (frequently <tt>/var/lib/squirrelmail/data/</tt>) must be owned by same user that owns other SquirrelMail scripts. The default preference file -and the default data directory must be readable and writable by webserver's -user. The webserver's user and the owner of the SquirrelMail scripts may be -different (e.g. in Debian, SquirrelMail is owned by root, but the webserver runs -as www-data). +and the default data directory must be readable and writable by the user that +the web server runs as. The user that the web server runs as and the owner of +the SquirrelMail scripts may be different (e.g. in Debian, SquirrelMail is +owned by root, but the web server runs as www-data). <sect1>UW IMAP <sect2>Login Disabled @@ -2791,8 +2958,8 @@ restrictions of SquirrelMail IMAP implementation. You may be able to use the IMAPS port of 993. -Please note, that if your IMAP server is on the same host as webserver with -SquirrelMail, SSL adds security features that are useless. During connection to +Please note, that if your IMAP server is on the same machine as the web server that +hosts SquirrelMail, SSL adds security features that are useless. During connection to localhost password information is not transmitted over unsafe network. If you want to secure your IMAP server, bind it to localhost address only or use tcpwrappers or firewall to disable external connections. @@ -2922,7 +3089,7 @@ The bug report plugin (bundled with SquirrelMail) collects a number of useful details, as does the -<tt>http://your-server/path-to-squirrelmail/src/configtest.php</tt> script +<tt>http://example.com/path-to-squirrelmail/src/configtest.php</tt> script script. Make sure that the data provided by at least one of these is part of your request for support. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2009-03-29 01:24:31
|
Revision: 13490 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13490&view=rev Author: pdontthink Date: 2009-03-29 01:24:25 +0000 (Sun, 29 Mar 2009) Log Message: ----------- Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-03-29 01:11:42 UTC (rev 13489) +++ trunk/documentation/admin/admin.sgml 2009-03-29 01:24:25 UTC (rev 13490) @@ -471,18 +471,20 @@ <p> Browse to http://example.com/squirrelmail/src/configtest.php to test your configuration for common errors. You'll need to adjust the -"squirrelmail" part to match the location where you installed it. Note that -in SquirrelMail versions 1.5.0 and up, if you are accessing configtest.php -from any place other than the machine where SquirrelMail is installed, you'll -need to make sure <tt>$allow_remote_configtest</tt> is enabled in your -configuration file to do so (or see "<tt>11. Tweaks</tt>" ==> -"<tt>7. Allow remote configtest</tt>" in the configuration utility). If you -do that, be sure to disable it again when you are finished. +"example.com" and "squirrelmail" parts to match the location where you +installed it. Note that in SquirrelMail versions 1.5.0 and up, if you are +accessing configtest.php from any place other than the machine where +SquirrelMail is installed, you'll need to make sure +<tt>$allow_remote_configtest</tt> is enabled in your configuration file to +do so (or see "<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" +in the configuration utility). If you do that, be sure to disable it again +when you are finished. <sect2>Log into SquirrelMail <p> Browse to http://example.com/squirrelmail/ to log in. Again, you'll need to -change "squirrelmail" to whatever the location is that you have it installed. +change "example.com" and "squirrelmail" to whatever the location is that you +have it installed. <sect1>Installing SquirrelMail on Unix and Linux systems <p> @@ -923,12 +925,12 @@ <tt>config/</tt> directory, go to <tt>http://example.com/squirrelmail/src/configtest.php</tt> and check if the configuration is correct so far. You'll need to -adjust the "squirrelmail" part to match the location where you -installed it. Note that in SquirrelMail versions 1.5.0 and up, -if you are accessing configtest.php -from any place other than the machine where SquirrelMail is installed, -you'll need to make sure <tt>$allow_remote_configtest</tt> is -enabled in your configuration file to do so (or see +adjust the "example.com" and "squirrelmail" parts to match the +location where you installed it. Note that in SquirrelMail versions +1.5.0 and up, if you are accessing configtest.php from any place other +than the machine where SquirrelMail is installed, you'll need to make +sure <tt>$allow_remote_configtest</tt> is enabled in your configuration +file to do so (or see "<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" in the configuration utility). If you do that, be sure to disable it again when you are finished. @@ -942,9 +944,9 @@ <p> Go to <tt>http://example.com/squirrelmail/src/login.php</tt> and try logging -in. You'll need to adjust the "squirrelmail" part to match the location -where you installed it. You should use a user name and password that -are known to work with your IMAP server. +in. You'll need to adjust the "example.com" and "squirrelmail" parts to +match the location where you installed it. You should use a user name +and password that are known to work with your IMAP server. <sect1>Prepackaged SquirrelMail installs <p> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <jer...@us...> - 2009-04-08 04:46:56
|
Revision: 13532 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13532&view=rev Author: jervfors Date: 2009-04-08 04:46:51 +0000 (Wed, 08 Apr 2009) Log Message: ----------- Some minor formatting. Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-04-06 19:06:45 UTC (rev 13531) +++ trunk/documentation/admin/admin.sgml 2009-04-08 04:46:51 UTC (rev 13532) @@ -449,12 +449,12 @@ not a problem or vulnerability, but some attackers have been known to snoop for old versions of SquirrelMail by trying to inspect things such as the ChangeLog file. If you want to employ the maximum level of protection against -snoops and would-be attackers, you can make use of the .htaccess files that +snoops and would-be attackers, you can make use of the <tt>.htaccess</tt> files that come with the SquirrelMail source code by adding "<tt>AllowOverride AuthConfig</tt>" to the <tt>Directory</tt> settings for SquirrelMail in your Apache configuration file (if using the Apache web server), or you can use the <tt>Directory</tt> settings suggested in the -<ref id="apache_configuration" name="apache configuration"> section below. +<ref id="apache_configuration" name="Apache configuration"> section below. <sect2>Configure SquirrelMail <p> @@ -469,11 +469,11 @@ <sect2>Check your SquirrelMail configuration <p> -Browse to http://example.com/squirrelmail/src/configtest.php +Browse to <tt>http://example.com/squirrelmail/src/configtest.php</tt> to test your configuration for common errors. You'll need to adjust the -"example.com" and "squirrelmail" parts to match the location where you +"<tt>example.com</tt>" and "<tt>squirrelmail</tt>" parts to match the location where you installed it. Note that in SquirrelMail versions 1.5.0 and up, if you are -accessing configtest.php from any place other than the machine where +accessing <tt>configtest.php</tt> from any place other than the machine where SquirrelMail is installed, you'll need to make sure <tt>$allow_remote_configtest</tt> is enabled in your configuration file to do so (or see "<tt>11. Tweaks</tt>" ==> "<tt>7. Allow remote configtest</tt>" @@ -482,8 +482,8 @@ <sect2>Log into SquirrelMail <p> -Browse to http://example.com/squirrelmail/ to log in. Again, you'll need to -change "example.com" and "squirrelmail" to whatever the location is that you +Browse to <tt>http://example.com/squirrelmail/</tt> to log in. Again, you'll need to +change "<tt>example.com</tt>" and "<tt>squirrelmail</tt>" to whatever the location is that you have it installed. <sect1>Installing SquirrelMail on Unix and Linux systems @@ -925,9 +925,9 @@ <tt>config/</tt> directory, go to <tt>http://example.com/squirrelmail/src/configtest.php</tt> and check if the configuration is correct so far. You'll need to -adjust the "example.com" and "squirrelmail" parts to match the +adjust the "<tt>example.com</tt>" and "<tt>squirrelmail</tt>" parts to match the location where you installed it. Note that in SquirrelMail versions -1.5.0 and up, if you are accessing configtest.php from any place other +1.5.0 and up, if you are accessing <tt>configtest.php</tt> from any place other than the machine where SquirrelMail is installed, you'll need to make sure <tt>$allow_remote_configtest</tt> is enabled in your configuration file to do so (or see @@ -944,7 +944,7 @@ <p> Go to <tt>http://example.com/squirrelmail/src/login.php</tt> and try logging -in. You'll need to adjust the "example.com" and "squirrelmail" parts to +in. You'll need to adjust the "<tt>example.com</tt>" and "<tt>squirrelmail</tt>" parts to match the location where you installed it. You should use a user name and password that are known to work with your IMAP server. @@ -1915,7 +1915,7 @@ <sect1>Mailbox format <p> -Default Unix mailbox format is slower than other formats and can increase server +The default Unix mailbox format is slower than other formats and can increase server loads when used with bigger mail folders. If you use UW IMAP server, you should try switching to mbx mailbox format. Maildir mailboxes have higher bottlenecks than formats that store entire mail folder in one file. @@ -2781,13 +2781,13 @@ <sect1>Configtest <p> When attempting to diagnose any issues with SquirrelMail, the first thing -to do is load up http://example.org/squirrelmail/src/configtest.php and ensure +to do is load up <tt>http://example.org/squirrelmail/src/configtest.php</tt> and ensure that SquirrelMail can't already tell you what the problem is. Note that as of SquirrelMail version 1.5.0, you cannot view this page from any computer other than the one where SquirrelMail is installed unless you have enabled remote computers to view it by using the SquirrelMail -configuration tool (config/conf.pl, which is usually aliased to "configure" +configuration tool (<tt>config/conf.pl</tt>, which is usually aliased to <tt>configure</tt> in the main SquirrelMail directory) and going to "11. Tweaks" and then chossing "7. Allow remote configtest". You can also edit the <tt/$allow_remote_configtest/ setting directly in <tt>config/config.php</tt> if you prefer. Before leaving @@ -2891,7 +2891,7 @@ <em>6. File ownership restrictions</em> -Default preference file (frequently named <tt/default_pref/) AND the default +The default preference file (frequently named <tt/default_pref/) AND the default data directory (frequently <tt>/var/lib/squirrelmail/data/</tt>) must be owned by same user that owns other SquirrelMail scripts. The default preference file and the default data directory must be readable and writable by the user that @@ -2972,6 +2972,9 @@ Folder Options. <sect1>Common interface error messages +<p> +TODO: Clean the "Common interface error messages" section up. + <sect2>Special folders (Sent/Drafts/Trash) are not translated <p> See <url url="http://squirrelmail.org/docs/translator/translator-3.html#ss3.6" name="http://squirrelmail.org/docs/translator/translator-3.html#ss3.6"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <jer...@us...> - 2009-04-10 15:27:27
|
Revision: 13536 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13536&view=rev Author: jervfors Date: 2009-04-10 15:27:21 +0000 (Fri, 10 Apr 2009) Log Message: ----------- Adding a FAQ about migration. Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-04-09 15:05:59 UTC (rev 13535) +++ trunk/documentation/admin/admin.sgml 2009-04-10 15:27:21 UTC (rev 13536) @@ -3024,8 +3024,44 @@ <sect>FAQ <p> -Daily questions +<descrip> + <tag>How do I migrate mails between servers?</tag><label id="mailmigration"> + If you have IMAP access besides SquirrelMail it's recommend to use a tool + dedicated to migration, such as <url + url="http://linux-france.org/prj/imapsync/" name="imapsync"> or <url + url="http://home.arcor.de/armin.diehl/imapcopy/imapcopy.html" + name="IMAPCopy">. IMAP copying/migration tools are available for various + platforms, so if none of those two fits your requirements, use a search + engine to find something to match your setup. + If you're migrating away from a POP3 server you might use the Mail Fetch + plugin (bundled with SquirrelMail). It'll transfer mail from your POP3 inbox + to your SquirrelMail installation, but it won't handle folders. + + If you're migrating away from SquirrelMail you can use the <url + url="http://squirrelmail.org/plugin_view.php?id=121" name="Archive Mail"> + plugin to download mails from the server, but there might not be an easy way + to upload those mails to the new server. + + Make sure that the ports needed to access the servers are open. The system + administrator have to help you if you don't have access to open them + yourself of if the system use any non-standard ports. + + The standard ports to use for clients and/or migration tools are: + <tabular ca="ll"> + <bf/Protocol/|<bf/Port/@ + IMAP|143@ + Secure IMAP (IMAP4-SSL)|585@ + IMAP4 over SSL (IMAPS)|993@ + POP3|110@ + Secure POP3 (SSL-POP)|995 + </tabular> + + Use the SquirrelMail <url + url="http://squirrelmail.org/plugin_view.php?id=29" name="Addressbook + Import-Export"> plugin to migrate the address book. +</descrip> + <sect>Support, feedback, and suggestions<label id="support"> <sect1>Before asking for support <p> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2009-04-14 10:12:14
|
Revision: 13539 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13539&view=rev Author: pdontthink Date: 2009-04-14 10:11:55 +0000 (Tue, 14 Apr 2009) Log Message: ----------- Enhance, fix. Question: should each FAQ have a sect tag? Without them, the questions won't appear in the TOC, which kinda sucks. Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-04-14 09:23:59 UTC (rev 13538) +++ trunk/documentation/admin/admin.sgml 2009-04-14 10:11:55 UTC (rev 13539) @@ -3026,26 +3026,41 @@ <p> <descrip> <tag>How do I migrate mails between servers?</tag><label id="mailmigration"> - If you have IMAP access besides SquirrelMail it's recommend to use a tool - dedicated to migration, such as <url - url="http://linux-france.org/prj/imapsync/" name="imapsync"> or <url + If you are able to access your IMAP server using means other than + SquirrelMail (that is, if your server's IMAP or IMAP-SSL ports are + available from your location), it is recommended that you use a dedicated + migration tool, such as <url url="http://linux-france.org/prj/imapsync/" + name="imapsync"> or <url url="http://home.arcor.de/armin.diehl/imapcopy/imapcopy.html" name="IMAPCopy">. IMAP copying/migration tools are available for various - platforms, so if none of those two fits your requirements, use a search + platforms, so if neither of these two fits your requirements, use a search engine to find something to match your setup. - If you're migrating away from a POP3 server you might use the Mail Fetch + If you are able to use another IMAP client (such as <url + url="http://www.mozilla.com/thunderbird" name="Thunderbird">) to access + mail on your servers, you can add both the new and old accounts to it + and drag and drop messages between the old and new accounts. Note that + this requires each user to set up and migrate their own messages - you + cannot migrate multiple user accounts automatically using this method. + + If you are migrating away from a POP3 server, you can use the Mail Fetch plugin (bundled with SquirrelMail). It'll transfer mail from your POP3 inbox - to your SquirrelMail installation, but it won't handle folders. + to your SquirrelMail installation, but it won't handle folders. Note that + this requires each user to set up and migrate their own messages; if you + need to automate the process for multiple users, use another tool or create + your own script to add the needed SquirrelMail settings for the Mail Fetch + plugin to each user's SquirrelMail preferences. If you're migrating away from SquirrelMail you can use the <url url="http://squirrelmail.org/plugin_view.php?id=121" name="Archive Mail"> plugin to download mails from the server, but there might not be an easy way to upload those mails to the new server. - Make sure that the ports needed to access the servers are open. The system - administrator have to help you if you don't have access to open them - yourself of if the system use any non-standard ports. + When using tools other than SquirrelMail, you'll probably need to make sure + that the ports needed to access the servers are open. The system + administrator may need to help you if you don't have the access or ability + to open them yourself (or if any of the systems you are working with use + any non-standard ports). The standard ports to use for clients and/or migration tools are: <tabular ca="ll"> @@ -3056,10 +3071,13 @@ POP3|110@ Secure POP3 (SSL-POP)|995 </tabular> +</descrip> +<descrip> + <tag>How do I migrate address books between servers?</tag><label id="abookmigration"> Use the SquirrelMail <url url="http://squirrelmail.org/plugin_view.php?id=29" name="Addressbook - Import-Export"> plugin to migrate the address book. + Import-Export"> plugin. </descrip> <sect>Support, feedback, and suggestions<label id="support"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: Fredrik J. <jer...@sq...> - 2009-04-15 22:57:44
|
> Revision: 13539 > http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13539&view=rev > Author: pdontthink > Date: 2009-04-14 10:11:55 +0000 (Tue, 14 Apr 2009) > > Log Message: > ----------- > Enhance, fix. Are you saying I'm not perfect? ;) Just kidding. Thanks. > Question: should each FAQ have a sect tag? Without them, the questions > won't appear in the TOC, which kinda sucks. Having them as sections was my first idea, but then I decided that it would look bad if there were too many FAQ added. Still, since there's only two right now, we might go for the sections now and move away from them when we actually _have_ too many FAQ. Sincerely, Fredrik |
From: Fredrik J. <jer...@sq...> - 2009-04-15 23:03:04
|
>> Question: should each FAQ have a sect tag? Without them, the questions >> won't appear in the TOC, which kinda sucks. > > Having them as sections was my first idea, but then I decided that it > would look bad if there were too many FAQ added. Still, since there's only > two right now, we might go for the sections now and move away from them > when we actually _have_ too many FAQ. Which, come to think of it, would break the links when moving from sections to descriptions. Sincerely, Fredrik |
From: Paul L. <pa...@sq...> - 2009-04-15 23:12:14
|
On Wed, Apr 15, 2009 at 4:02 PM, Fredrik Jervfors <jer...@sq...> wrote: >>> Question: should each FAQ have a sect tag? Without them, the questions >>> won't appear in the TOC, which kinda sucks. >> >> Having them as sections was my first idea, but then I decided that it >> would look bad if there were too many FAQ added. Still, since there's only >> two right now, we might go for the sections now and move away from them >> when we actually _have_ too many FAQ. > > Which, come to think of it, would break the links when moving from > sections to descriptions. You mean links that places like Google have cached? Cuz the sgml of course builds the links automagically. We can also use anchor tags that will remain static but don't have anything to do with the TOC links/issue. I understand what you're saying about crowding the TOC, but I think that not having an indexed FAQ is a bigger problem, and even if the TOC is too long when we have a LOT of FAQs, it will be an even bigger problem that we don't have them indexed.... that is to say, even if we have 100 FAQs, I think it would be best to have them in the TOC (short of some other system where we can index them somewhere other than the TOC). Maybe another option is to make each FAQ a <sect2> and create top-level categories as <sect> so only the categories show in the TOC. I'd still like it better if the questions themselves are indexed I think. |
From: Fredrik J. <jer...@sq...> - 2009-04-15 23:25:25
|
>>>> Question: should each FAQ have a sect tag? Without them, the >>>> questions won't appear in the TOC, which kinda sucks. >>> >>> Having them as sections was my first idea, but then I decided that it >>> would look bad if there were too many FAQ added. Still, since >>> there's only two right now, we might go for the sections now and move >>> away from them when we actually _have_ too many FAQ. >> >> Which, come to think of it, would break the links when moving from >> sections to descriptions. > > You mean links that places like Google have cached? Cuz the sgml of > course builds the links automagically. We can also use anchor tags that > will remain static but don't have anything to do with the TOC links/issue. > > I understand what you're saying about crowding the TOC, but I think > that not having an indexed FAQ is a bigger problem, and even if the TOC is > too long when we have a LOT of FAQs, it will be an even bigger problem > that we don't have them indexed.... that is to say, even if we have 100 > FAQs, I think it would be best to have them in the TOC > (short of some other system where we can index them somewhere other > than the TOC). Maybe another option is to make each FAQ a <sect2> and > create top-level categories as <sect> so only the categories show in the > TOC. I'd still like it better if the questions themselves are > indexed I think. Sure, some sort of index is usually useful. I won't oppose if you'll implement your suggestion. Sincerely, Fredrik |
From: Paul L. <pa...@sq...> - 2009-04-16 01:20:25
|
On Wed, Apr 15, 2009 at 4:25 PM, Fredrik Jervfors <jer...@sq...> wrote: >>>>> Question: should each FAQ have a sect tag? Without them, the >>>>> questions won't appear in the TOC, which kinda sucks. >>>> >>>> Having them as sections was my first idea, but then I decided that it >>>> would look bad if there were too many FAQ added. Still, since >>>> there's only two right now, we might go for the sections now and move >>>> away from them when we actually _have_ too many FAQ. >>> >>> Which, come to think of it, would break the links when moving from >>> sections to descriptions. >> >> You mean links that places like Google have cached? Cuz the sgml of >> course builds the links automagically. We can also use anchor tags that >> will remain static but don't have anything to do with the TOC links/issue. >> >> I understand what you're saying about crowding the TOC, but I think >> that not having an indexed FAQ is a bigger problem, and even if the TOC is >> too long when we have a LOT of FAQs, it will be an even bigger problem >> that we don't have them indexed.... that is to say, even if we have 100 >> FAQs, I think it would be best to have them in the TOC >> (short of some other system where we can index them somewhere other >> than the TOC). Maybe another option is to make each FAQ a <sect2> and >> create top-level categories as <sect> so only the categories show in the >> TOC. I'd still like it better if the questions themselves are >> indexed I think. > > Sure, some sort of index is usually useful. I won't oppose if you'll > implement your suggestion. Alright, I will commit it as sect1 for each FAQ. If anyone has better ideas..... |
From: <pdo...@us...> - 2009-04-16 01:55:07
|
Revision: 13550 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13550&view=rev Author: pdontthink Date: 2009-04-16 01:34:07 +0000 (Thu, 16 Apr 2009) Log Message: ----------- Give each FAQ a TOC entry Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-04-15 22:00:49 UTC (rev 13549) +++ trunk/documentation/admin/admin.sgml 2009-04-16 01:34:07 UTC (rev 13550) @@ -3023,10 +3023,12 @@ Some quota setups can ignore files placed in Trash folder. <sect>FAQ + +<sect1>How do I migrate mails between servers?<label id="mailmigration"> <p> -<descrip> - <tag>How do I migrate mails between servers?</tag><label id="mailmigration"> - If you are able to access your IMAP server using means other than +Here are several options for your consideration: +<itemize> + <item>If you are able to access your IMAP server using means other than SquirrelMail (that is, if your server's IMAP or IMAP-SSL ports are available from your location), it is recommended that you use a dedicated migration tool, such as <url url="http://linux-france.org/prj/imapsync/" @@ -3035,50 +3037,54 @@ name="IMAPCopy">. IMAP copying/migration tools are available for various platforms, so if neither of these two fits your requirements, use a search engine to find something to match your setup. +</itemize> - If you are able to use another IMAP client (such as <url +<itemize> + <item>If you are able to use another IMAP client (such as <url url="http://www.mozilla.com/thunderbird" name="Thunderbird">) to access mail on your servers, you can add both the new and old accounts to it and drag and drop messages between the old and new accounts. Note that this requires each user to set up and migrate their own messages - you cannot migrate multiple user accounts automatically using this method. +</itemize> - If you are migrating away from a POP3 server, you can use the Mail Fetch +<itemize> + <item>If you are migrating away from a POP3 server, you can use the Mail Fetch plugin (bundled with SquirrelMail). It'll transfer mail from your POP3 inbox to your SquirrelMail installation, but it won't handle folders. Note that this requires each user to set up and migrate their own messages; if you need to automate the process for multiple users, use another tool or create your own script to add the needed SquirrelMail settings for the Mail Fetch plugin to each user's SquirrelMail preferences. +</itemize> - If you're migrating away from SquirrelMail you can use the <url +<itemize> + <item>If you're migrating away from SquirrelMail you can use the <url url="http://squirrelmail.org/plugin_view.php?id=121" name="Archive Mail"> plugin to download mails from the server, but there might not be an easy way to upload those mails to the new server. +</itemize> - When using tools other than SquirrelMail, you'll probably need to make sure - that the ports needed to access the servers are open. The system - administrator may need to help you if you don't have the access or ability - to open them yourself (or if any of the systems you are working with use - any non-standard ports). +When using tools other than SquirrelMail, you'll probably need to make sure +that the ports needed to access the servers are open. The system +administrator may need to help you if you don't have the access or ability +to open them yourself (or if any of the systems you are working with use +any non-standard ports). - The standard ports to use for clients and/or migration tools are: - <tabular ca="ll"> - <bf/Protocol/|<bf/Port/@ - IMAP|143@ - Secure IMAP (IMAP4-SSL)|585@ - IMAP4 over SSL (IMAPS)|993@ - POP3|110@ - Secure POP3 (SSL-POP)|995 - </tabular> -</descrip> +The standard ports to use for clients and/or migration tools are: +<tabular ca="ll"> + <bf/Protocol/|<bf/Port/@ + IMAP|143@ + Secure IMAP (IMAP4-SSL)|585@ + IMAP4 over SSL (IMAPS)|993@ + POP3|110@ + Secure POP3 (SSL-POP)|995 +</tabular> -<descrip> - <tag>How do I migrate address books between servers?</tag><label id="abookmigration"> - Use the SquirrelMail <url - url="http://squirrelmail.org/plugin_view.php?id=29" name="Addressbook - Import-Export"> plugin. -</descrip> +<sect1>How do I migrate address books between servers?<label id="abookmigration"> +<p> +Use the SquirrelMail <url url="http://squirrelmail.org/plugin_view.php?id=29" +name="Addressbook Import-Export"> plugin. <sect>Support, feedback, and suggestions<label id="support"> <sect1>Before asking for support This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: Fredrik J. <jer...@sq...> - 2009-04-16 22:59:00
|
> Revision: 13550 > http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13550&view=rev > Author: pdontthink > Date: 2009-04-16 01:34:07 +0000 (Thu, 16 Apr 2009) > > Log Message: > ----------- > Give each FAQ a TOC entry Sweet! But shouldn't the list of options in <http://squirrelmail.org/docs/admin/admin-11.html#ss11.2> be one list instead of four lists? If white space is the concern my humble opinion is that is should be fixed using CSS if possible. Is it OK if I make it one list with four items instead of four lists with one item? > Modified Paths: > -------------- > trunk/documentation/admin/admin.sgml > > Modified: trunk/documentation/admin/admin.sgml > =================================================================== > --- trunk/documentation/admin/admin.sgml 2009-04-15 22:00:49 UTC (rev > 13549) > +++ trunk/documentation/admin/admin.sgml 2009-04-16 01:34:07 UTC (rev > 13550) > @@ -3023,10 +3023,12 @@ > Some quota setups can ignore files placed in Trash folder. > > > <sect>FAQ > + > +<sect1>How do I migrate mails between servers?<label id="mailmigration"> > <p> > -<descrip> > - <tag>How do I migrate mails between servers?</tag><label > id="mailmigration"> - If you are able to access your IMAP server using > means other than +Here are several options for your consideration: > +<itemize> > + <item>If you are able to access your IMAP server using means other than > SquirrelMail (that is, if your server's IMAP or IMAP-SSL ports are > available from your location), it is recommended that you use a dedicated > migration tool, such as <url url="http://linux-france.org/prj/imapsync/" > @@ -3035,50 +3037,54 @@ > name="IMAPCopy">. IMAP copying/migration tools are available for various > platforms, so if neither of these two fits your requirements, use a > search engine to find something to match your setup. +</itemize> > > > - If you are able to use another IMAP client (such as <url > +<itemize> > + <item>If you are able to use another IMAP client (such as <url > url="http://www.mozilla.com/thunderbird" name="Thunderbird">) to access > mail on your servers, you can add both the new and old accounts to it and > drag and drop messages between the old and new accounts. Note that this > requires each user to set up and migrate their own messages - you cannot > migrate multiple user accounts automatically using this method. > +</itemize> > > > - If you are migrating away from a POP3 server, you can use the Mail > Fetch > +<itemize> > + <item>If you are migrating away from a POP3 server, you can use the > Mail Fetch > plugin (bundled with SquirrelMail). It'll transfer mail from your POP3 > inbox to your SquirrelMail installation, but it won't handle folders. Note > that this requires each user to set up and migrate their own messages; if > you need to automate the process for multiple users, use another tool or > create your own script to add the needed SquirrelMail settings for the > Mail Fetch > plugin to each user's SquirrelMail preferences. +</itemize> > > > - If you're migrating away from SquirrelMail you can use the <url > +<itemize> > + <item>If you're migrating away from SquirrelMail you can use the <url > url="http://squirrelmail.org/plugin_view.php?id=121" name="Archive Mail"> > plugin to download mails from the server, but there might not be an easy > way to upload those mails to the new server. +</itemize> > > > - When using tools other than SquirrelMail, you'll probably need to > make sure - that the ports needed to access the servers are open. The > system - administrator may need to help you if you don't have the > access or ability - to open them yourself (or if any of the systems you > are working with use - any non-standard ports). > +When using tools other than SquirrelMail, you'll probably need to make > sure +that the ports needed to access the servers are open. The system > +administrator may need to help you if you don't have the access or > ability +to open them yourself (or if any of the systems you are working > with use +any non-standard ports). > > > - The standard ports to use for clients and/or migration tools are: > - <tabular ca="ll"> > - <bf/Protocol/|<bf/Port/@ > - IMAP|143@ > - Secure IMAP (IMAP4-SSL)|585@ > - IMAP4 over SSL (IMAPS)|993@ > - POP3|110@ > - Secure POP3 (SSL-POP)|995 > - </tabular> > -</descrip> > +The standard ports to use for clients and/or migration tools are: > +<tabular ca="ll"> > + <bf/Protocol/|<bf/Port/@ > + IMAP|143@ > + Secure IMAP (IMAP4-SSL)|585@ > + IMAP4 over SSL (IMAPS)|993@ > + POP3|110@ > + Secure POP3 (SSL-POP)|995 > +</tabular> > > > -<descrip> > - <tag>How do I migrate address books between servers?</tag><label > id="abookmigration"> - Use the SquirrelMail <url > - url="http://squirrelmail.org/plugin_view.php?id=29" name="Addressbook > - Import-Export"> plugin. > -</descrip> > +<sect1>How do I migrate address books between servers?<label > id="abookmigration"> +<p> > +Use the SquirrelMail <url > url="http://squirrelmail.org/plugin_view.php?id=29" > +name="Addressbook Import-Export"> plugin. > > > <sect>Support, feedback, and suggestions<label id="support"> > <sect1>Before asking for support > > > > This was sent by the SourceForge.net collaborative development platform, > the world's largest Open Source development site. > > ------------------------------------------------------------------------- > ----- > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save $200 on the > JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > ----- > squirrelmail-cvs mailing list List address: > squ...@li... List info > (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-cvs > Repository: http://squirrelmail.org/svn > > |
From: Paul L. <pa...@sq...> - 2009-04-16 23:27:19
|
On Thu, Apr 16, 2009 at 3:58 PM, Fredrik Jervfors <jer...@sq...> wrote: >> Revision: 13550 >> http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13550&view=rev >> Author: pdontthink >> Date: 2009-04-16 01:34:07 +0000 (Thu, 16 Apr 2009) >> >> Log Message: >> ----------- >> Give each FAQ a TOC entry > > Sweet! But shouldn't the list of options in > <http://squirrelmail.org/docs/admin/admin-11.html#ss11.2> be one list > instead of four lists? If white space is the concern my humble opinion is > that is should be fixed using CSS if possible. Is it OK if I make it one > list with four items instead of four lists with one item? Yes it should be one list. However, I found it nearly unreadable without the needed whitespace. Maybe it could be hacked by adding an empty <tscreen> or something, as the list in 11.1 with <tscreen>s is nicely spaced. |
From: <pdo...@us...> - 2009-04-16 02:31:50
|
Revision: 13551 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13551&view=rev Author: pdontthink Date: 2009-04-16 02:31:47 +0000 (Thu, 16 Apr 2009) Log Message: ----------- Adding blank page FAQ Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-04-16 01:34:07 UTC (rev 13550) +++ trunk/documentation/admin/admin.sgml 2009-04-16 02:31:47 UTC (rev 13551) @@ -3024,6 +3024,74 @@ <sect>FAQ +<sect1>How can I diagnose blank pages?<label id="blankpage"> +<p> +Under some circumstances, a page request can result in nothing more than +a blank page. In most cases, this happens after the installation of a +plugin, but it can happen elsewhere as well. This problem is typically caused +by fatal PHP errors that are simply not being shown on screen. + +You can find those errors by looking in your web server log file. The +location of that file will be different on some machines, but one +example is <tt>/var/log/httpd/error_log</tt>. + +Alternatively, you can tell PHP to display the errors on screen in one +of a few ways described below (remember to turn them off again if you +are doing this in a production environment): + +<itemize> + <item>Change the error reporting settings in <tt/php.ini/ (remember to + restart the web server after you make changes to <tt/php.ini/): + <tscreen><verb> + display_errors=On + error_reporting=E_ALL + </verb></tscreen> + <item>Change the error reporting settings just for SquirrelMail by + adding the following lines into an <tt/.htaccess/ file in the + main SquirrelMail directory (this is an Apache web server + feature that also requires that you have at least + "<tt/AllowOverride Options/" in the <tt><Directory></tt> + section that applies to your SquirrelMail installation + within the Apache configuration file). + <tscreen><verb> + php_flag display_errors On + php_value error_reporting E_ALL + </verb></tscreen> + <item>Install the SquirrelMail + <url url="http://squirrelmail.org/plugin_view.php?id=228" + name="Debugger plugin"> +</itemize> + +Note that if you still have trouble seeing errors on screen, make sure +you have not overridden the error reporting settings in your Apache +configuration file or in another .htaccess file or custom SquirrelMail +plugin, etc. + +Some more common causes of blank pages are: + +<itemize> + <item>You installed a new plugin but forgot to install one of + its dependencies (such as the <url + url="http://squirrelmail.org/plugin_view.php?id=152" + name="Compatibility plugin">) or apply a required patch. + Please carefully consult all the documentation files that + came with your new plugin, including its <tt/README/ and + <tt/INSTALL/ files. + <item>You are attempting to view a folder with a very large number + of messages in it (perhaps as many as 10,000). In this case, + you may hit the maximum PHP execution time limit or maximum + memory limit. If you find such errors, you may want to + review our <ref id="optimization" name="optimization tips"> + or our <url url="http://squirrelmail.org/wiki/SquirrelMailPerformance" + name="performance hints">. + <item>You have installed SquirrelMail for the first time and it does + not work at all - even the configuration test page and the login + page come up blank. This can be caused by the lack of session + support in PHP (which SquirrelMail requires). See the + <url url="http://php.net/manual/session.installation.php" + name="PHP session extension installation manual">. +</itemize> + <sect1>How do I migrate mails between servers?<label id="mailmigration"> <p> Here are several options for your consideration: This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <jer...@us...> - 2009-05-31 10:06:28
|
Revision: 13774 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13774&view=rev Author: jervfors Date: 2009-05-31 10:06:17 +0000 (Sun, 31 May 2009) Log Message: ----------- Implementing a suggestion from Rajiv Manglani (#1808989). Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-05-31 10:03:06 UTC (rev 13773) +++ trunk/documentation/admin/admin.sgml 2009-05-31 10:06:17 UTC (rev 13774) @@ -55,7 +55,8 @@ <p> There are only two requirements for SquirrelMail: <itemize> - <item>A web server with PHP installed. PHP needs to be at least 4.1.0. + <item>A web server with PHP installed. PHP needs to be at least 4.1.0. PHP 4, + PHP 5 and PHP 6 are all supported. <item>Access to an IMAP server which supports IMAP 4 rev 1. </itemize> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <jer...@us...> - 2009-08-01 15:40:47
|
Revision: 13807 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13807&view=rev Author: jervfors Date: 2009-08-01 15:40:38 +0000 (Sat, 01 Aug 2009) Log Message: ----------- Closing the Spanish mailing list. Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-07-31 10:12:46 UTC (rev 13806) +++ trunk/documentation/admin/admin.sgml 2009-08-01 15:40:38 UTC (rev 13807) @@ -3391,7 +3391,7 @@ SquirrelMail CVS Mailing List (legacy name)|Messages are sent with every change in the repository.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-cvs" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-cvs" name="S"> <url url="http://marc.info/?l=squirrelmail-cvs" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.cvs" name="G"> N@ SquirrelMail Development Mailing List|For discussing the development of SquirrelMail and patches.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-devel" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-devel" name="S"> <url url="http://marc.info/?l=squirrelmail-devel" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.devel" name="G"> <url url="http://www.nabble.com/squirrelmail-devel-f4374.html" name="N">@ SquirrelMail Internationalization Mailing List|Questions and discussions concerning translations, character sets, etc.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-i18n" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-i18n" name="S"> <url url="http://marc.info/?l=squirrelmail-i18n" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.internationalization" name="G"> <url url="http://www.nabble.com/squirrelmail-i18n-f4375.html" name="N">@ -SquirrelMail Mailing List in Spanish|For those of us who prefer Spanish.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-lang-es" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-lang-es" name="S"> <url url="http://marc.info/?l=squirrelmail-lang-es" name="M"> G <url url="http://www.nabble.com/squirrelmail-lang-es-f4376.html" name="N">@ +SquirrelMail Mailing List in Spanish|This list is inactive, but the archives still exist.|Inactive|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-lang-es" name="S"> <url url="http://marc.info/?l=squirrelmail-lang-es" name="M"> G <url url="http://www.nabble.com/squirrelmail-lang-es-f4376.html" name="N">@ SquirrelMail Plugins Mailing List|For help with using and developing SquirrelMail plugins.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-plugins" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-plugins" name="S"> <url url="http://marc.info/?l=squirrelmail-plugins" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.plugins" name="G"> <url url="http://www.nabble.com/squirrelmail-plugins-f4377.html" name="N">@ SquirrelMail Stable Series Mailing List|This list is inactive, but the archives still exist.|Inactive|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-stable" name="S"> <url url="http://marc.info/?l=squirrelmail-stable" name="M"> G N@ SquirrelMail Users Mailing List (legacy name)|Despite its name, this list is intended for supporting administrators and not end users. This is the main list, dealing mostly with administrating SquirrelMail and general feedback.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-users" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-users" name="S"> <url url="http://marc.info/?l=squirrelmail-users" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.user" name="G"> <url url="http://www.nabble.com/squirrelmail-users-f4380.html" name="N"> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <jer...@us...> - 2009-10-28 12:47:53
|
Revision: 13869 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13869&view=rev Author: jervfors Date: 2009-10-28 12:47:43 +0000 (Wed, 28 Oct 2009) Log Message: ----------- Adding a warning about configuration changes. Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2009-10-28 12:11:56 UTC (rev 13868) +++ trunk/documentation/admin/admin.sgml 2009-10-28 12:47:43 UTC (rev 13869) @@ -1335,6 +1335,10 @@ file manually. The first of these ways is the one recommended by the SquirrelMail Project. +Please note that if there are users logged in when the configuration is changed, +those users might not be affected by the changes until after they have logged +out. This is a side effect of the caching of data for logged in users. + <sect2>The configuration tool <p> Included in the SquirrelMail distribution is a Perl script, located at This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2010-05-09 20:23:57
|
Revision: 13937 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13937&view=rev Author: pdontthink Date: 2010-05-09 20:23:50 +0000 (Sun, 09 May 2010) Log Message: ----------- Fix Nabble links Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2010-05-07 19:06:56 UTC (rev 13936) +++ trunk/documentation/admin/admin.sgml 2010-05-09 20:23:50 UTC (rev 13937) @@ -3391,18 +3391,18 @@ <tabular ca="lccc"> <bf/Mailing list/|<bf/Description/|<bf/Subscribe/|<bf/Archives/@ -SquirrelMail Announcement Mailing List|Very low traffic, moderated, announcements only.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-announce" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-announce" name="S"> <url url="http://marc.info/?l=squirrelmail-announce" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.announce" name="G"> <url url="http://www.nabble.com/squirrelmail-announce-f4373.html" name="N">@ +SquirrelMail Announcement Mailing List|Very low traffic, moderated, announcements only.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-announce" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-announce" name="S"> <url url="http://marc.info/?l=squirrelmail-announce" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.announce" name="G"> <url url="http://old.nabble.com/squirrelmail-announce-f4373.html" name="N">@ SquirrelMail CVS Mailing List (legacy name)|Messages are sent with every change in the repository.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-cvs" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-cvs" name="S"> <url url="http://marc.info/?l=squirrelmail-cvs" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.cvs" name="G"> N@ -SquirrelMail Development Mailing List|For discussing the development of SquirrelMail and patches.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-devel" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-devel" name="S"> <url url="http://marc.info/?l=squirrelmail-devel" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.devel" name="G"> <url url="http://www.nabble.com/squirrelmail-devel-f4374.html" name="N">@ -SquirrelMail Internationalization Mailing List|Questions and discussions concerning translations, character sets, etc.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-i18n" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-i18n" name="S"> <url url="http://marc.info/?l=squirrelmail-i18n" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.internationalization" name="G"> <url url="http://www.nabble.com/squirrelmail-i18n-f4375.html" name="N">@ -SquirrelMail Mailing List in Spanish|This list is inactive, but the archives still exist.|Inactive|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-lang-es" name="S"> <url url="http://marc.info/?l=squirrelmail-lang-es" name="M"> G <url url="http://www.nabble.com/squirrelmail-lang-es-f4376.html" name="N">@ -SquirrelMail Plugins Mailing List|For help with using and developing SquirrelMail plugins.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-plugins" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-plugins" name="S"> <url url="http://marc.info/?l=squirrelmail-plugins" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.plugins" name="G"> <url url="http://www.nabble.com/squirrelmail-plugins-f4377.html" name="N">@ +SquirrelMail Development Mailing List|For discussing the development of SquirrelMail and patches.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-devel" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-devel" name="S"> <url url="http://marc.info/?l=squirrelmail-devel" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.devel" name="G"> <url url="http://old.nabble.com/squirrelmail-devel-f4374.html" name="N">@ +SquirrelMail Internationalization Mailing List|Questions and discussions concerning translations, character sets, etc.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-i18n" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-i18n" name="S"> <url url="http://marc.info/?l=squirrelmail-i18n" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.internationalization" name="G"> <url url="http://old.nabble.com/squirrelmail-i18n-f4375.html" name="N">@ +SquirrelMail Mailing List in Spanish|This list is inactive, but the archives still exist.|Inactive|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-lang-es" name="S"> <url url="http://marc.info/?l=squirrelmail-lang-es" name="M"> G <url url="http://old.nabble.com/squirrelmail-lang-es-f4376.html" name="N">@ +SquirrelMail Plugins Mailing List|For help with using and developing SquirrelMail plugins.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-plugins" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-plugins" name="S"> <url url="http://marc.info/?l=squirrelmail-plugins" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.plugins" name="G"> <url url="http://old.nabble.com/squirrelmail-plugins-f4377.html" name="N">@ SquirrelMail Stable Series Mailing List|This list is inactive, but the archives still exist.|Inactive|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-stable" name="S"> <url url="http://marc.info/?l=squirrelmail-stable" name="M"> G N@ -SquirrelMail Users Mailing List (legacy name)|Despite its name, this list is intended for supporting administrators and not end users. This is the main list, dealing mostly with administrating SquirrelMail and general feedback.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-users" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-users" name="S"> <url url="http://marc.info/?l=squirrelmail-users" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.user" name="G"> <url url="http://www.nabble.com/squirrelmail-users-f4380.html" name="N"> +SquirrelMail Users Mailing List (legacy name)|Despite its name, this list is intended for supporting administrators and not end users. This is the main list, dealing mostly with administrating SquirrelMail and general feedback.|<url url="http://lists.sourceforge.net/mailman/listinfo/squirrelmail-users" name="Subscribe">|<url url="http://sourceforge.net/mailarchive/forum.php?forum_name=squirrelmail-users" name="S"> <url url="http://marc.info/?l=squirrelmail-users" name="M"> <url url="http://dir.gmane.org/gmane.mail.squirrelmail.user" name="G"> <url url="http://old.nabble.com/squirrelmail-users-f4380.html" name="N"> </tabular> Legend: S = SourceForge, M = MARC, G = Gmane, N = Nabble (there's also an <url -url="http://www.nabble.com/SquirrelMail-f4372.html" name="all-in-one"> +url="http://old.nabble.com/SquirrelMail-f4372.html" name="all-in-one"> interface for all list archives at Nabble). The subscription interface for <url This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <pdo...@us...> - 2010-07-21 07:22:56
|
Revision: 13964 http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13964&view=rev Author: pdontthink Date: 2010-07-21 07:22:49 +0000 (Wed, 21 Jul 2010) Log Message: ----------- The use of 'user' as a column name no longer causes errors in SquirrelMail Modified Paths: -------------- trunk/documentation/admin/admin.sgml Modified: trunk/documentation/admin/admin.sgml =================================================================== --- trunk/documentation/admin/admin.sgml 2010-07-21 07:06:12 UTC (rev 13963) +++ trunk/documentation/admin/admin.sgml 2010-07-21 07:22:49 UTC (rev 13964) @@ -1699,15 +1699,20 @@ and for PostgreSQL: <tscreen><verb> --- Note: Change the SquirrelMail config variable $prefs_user_field in --- "config/config.php" from the default "user" to "username" since "user" --- is a reserved word in PostgreSQL. CREATE TABLE "userprefs" ( - "username" varchar(128) NOT NULL, + "user" varchar(128) NOT NULL, "prefkey" varchar(64) NOT NULL, "prefval" text, CONSTRAINT "userprefs_pkey" PRIMARY KEY ("prefkey", "username") ); + +-- Note: "user" is a reserved keyword in PostgreSQL and it could cause +-- problems when it is used as a column name as above. SquirrelMail +-- knows about this issue and should work OK with "user", but if you +-- decide to change it to something else (such as "username"), you'll +-- also need to change the SquirrelMail config variable $prefs_user_field +-- in "config/config.php" to match (or use the configuration tool, +-- 9. Database --> 5. Field for username). </verb></tscreen> Note the difference in the table column definitions between the MySQL and the This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |