Introduction:
-------------
-SquirrelMail is a standards-based webmail package written in PHP4. It includes
-built-in pure PHP support for the IMAP and SMTP protocols, and all pages render
-in pure HTML 4.0 (with no Javascript) for maximum compatibility across
-browsers. It has very few requirements and is very easy to configure and
-install. SquirrelMail has a all the functionality you would want from an email
-client, including strong MIME support, address books, and folder manipulation.
-
-Why did you guys create SquirrelMail? The need arose in our organization for
-the access of email and address books from anywhere in the world. Obviously
-a web interface is ideal for this, given that the user has access to the
-Internet. After reviewing several open source projects, we realized that
-we were going to need to do some fairly major customizations to get things
-to be a nice fit for our needs. So the decision was made to create our
-own for some of these reasons, and for fun (we really like PHP4). We
-decided to open source the project to contribute to the community that has
-contributed so much to us. Since then, it has grown much bigger than we ever
-imagined, and we have an awesome development team who are actively working
-on the project.
+SquirrelMail is a standards-based webmail package written in PHP4. It
+includes built-in pure PHP support for the IMAP and SMTP protocols, and all
+pages render in pure HTML 4.0 (with no Javascript) for maximum compatibility
+across browsers. It has very few requirements and is very easy to configure
+and install. SquirrelMail has a all the functionality you would want from an
+email client, including strong MIME support, address books, and folder
+manipulation.
+
+Why did you guys create SquirrelMail? The need arose in our organization
+for the access of email and address books from anywhere in the world.
+Obviously a web interface is ideal for this, given that the user has access
+to the Internet. After reviewing several open source projects, we realized
+that we were going to need to do some fairly major customizations to get
+things to be a nice fit for our needs. So the decision was made to create
+our own for some of these reasons, and for fun (we really like PHP4). We
+decided to open source the project to contribute to the community that has
+contributed so much to us. Since then, it has grown much bigger than we
+ever imagined, and we have an awesome development team who are actively
+working on the project.
We would love to hear from you! The nature of open source projects make it
hard to know who all is using your product. It is always nice when we get
emails from people just telling us that they're using SquirrelMail. If you
-have a few minutes, please send us an email to let us know! You can send
-it to our mailing list: squirrelmail-list@sourceforge.net
+have a few minutes, please send us an email to let us know! You can send it
+to our mailing list: squirrelmail-list@sourceforge.net
You can also go to the page below and fill out a small form to get listed
with the list of people already using SquirrelMail (free advertising).
--------
It is pretty easy to get in contact with the developers if you need help or
if you find bugs that need to be reported. The best way to contact us would
-be through our mailing list which is actively monitored. Just send an
-email to:
+be through our mailing list which is actively monitored. Just send an email
+to:
squirrelmail-list@sourceforge.net
Installation:
-------------
- For detailed instructions on how to install SquirrelMail on your server,
- please refer to the INSTALL document in the same directory as this document.
+For detailed instructions on how to install SquirrelMail on your server,
+please refer to the INSTALL document in the same directory as this document.
Licensing:
----------
- This product is distributed under the GPL. Please read through the file
- COPYING for more information about our license.
+This product is distributed under the GPL. Please read through the file
+COPYING for more information about our license.
Upgrading from 0.3 or 0.4
=========================
-If you are upgrading from versions 0.3 or 0.4 of SquirrelMail, you can use this
-guide to make the transition a bit smoother. If you have been using a previous
-version (0.1 or 0.2), it is suggested that you just start from scratch and
-configure your settings as if it was your first install.
+If you are upgrading from versions 0.3 or 0.4 of SquirrelMail, you can use
+this guide to make the transition a bit smoother. If you have been using a
+previous version (0.1 or 0.2), it is suggested that you just start from
+scratch and configure your settings as if it was your first install.
-NOTE: The new plugin architecture required the use of some functions which are
-not in all versions of PHP4. You will need at least PHP4 beta2. If you need to
-upgrade please go ahead and install the latest release version of PHP4.
+NOTE: The new plugin architecture required the use of some functions which
+are not in all versions of PHP4. You will need at least PHP4 beta2. If you
+need to upgrade please go ahead and install the latest release version of
+PHP4.
1. Backups
===========
-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. In this example, we assume that your httpd document directory
-is /home/httpd/html.
+
+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. In this example, we assume that your httpd
+document directory is /home/httpd/html.
$ cd /home/httpd/html
$ cp -Rp squirrelmail-0.4 squirrelmail-0.4.bak
2. Unarchives Squirrelmail-0.5.tar.gz
======================================
-Make sure that you're in your httpd document directory (/home/httpd/html) and
-then unarchive the squirrelmail archive (whatever the filename is):
-
+Make sure that you're in your httpd document directory (/home/httpd/html)
+and then unarchive the squirrelmail archive (whatever the filename is):
+
$ tar -zxvf squirrelmail-0.5.tar.gz
3. Copy backups in place
=========================
Here is the main part. There are two parts to this step: copy preferences,
-and copy config details. The preference files are backwards compatible, so it
-is fine to copy the old user preferences into the new directory. However, the
-configuration file has changed quite a bit, so you will want to be sure to run
-the configure script (conf.pl) to set up any new config details.
+and copy config details. The preference files are backwards compatible, so
+it is fine to copy the old user preferences into the new directory.
+However, the configuration file has changed quite a bit, so you will want to
+be sure to run the configure script (conf.pl) to set up any new config
+details.
First, copy the files in place:
5. DONE!
=========
-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.
+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.
projects / squirrelmail.git / commitdiff