+ If you have a database like MySQL you might want to add something
+ like --with-mysql to get database functionality.
+
+ Run make to build the binary file. This will generate a binary file
+ called "php". Move this file into a CGI-directory.
+
+ You might also want to read the INSTALL file in the PHP-distribution
+ :-)
+
+b. Setting up .php files to use PHP4
+
+ You need to create a .htaccess file in you SquirrelMail directory
+ that looks something like this:
+
+ AddType application/php4script .php
+ Action application/php4script /cgi-bin/php
+
+ You could also add these lines to your Apache configuration file.
+
+c. Running into trouble
+
+ Setting up Apache with PHP4 can be a non-trivial task. Read the PHP4
+ and Apache documentation carefully if you run into trouble. If you
+ have an experienced system administrator around ask her/him to help
+ you.
+
+2. SETTING UP IMAP
+------------------
+
+ This is not covered here :-/
+
+3. OBTAINING AND INSTALLING SQUIRRELMAIL
+----------------------------------------
+
+ SquirrelMail is still under development. Therefore you should always
+ get the newest version around. Look at
+ http://squirrelmail.sourceforge.net/index.php3?page=5 to see what it
+ is. If you want to be bleeding edge you might want to consider using
+ the latest CVS version (with the latest and most fashionable of
+ bugs).
+
+a. Download SquirrelMail
+
+ Get SquirrelMail from the address above if you do not have it or are
+ uncertain if you have the newest version. Untar (again tar xvfz
+ filename.tgz) SquirrelMail in a directory that is readable for your
+ webserver.
+
+b. Setting up directories
+
+ SquirrelMail uses two directories to store user configuration and
+ attachments that are about to be sent. You might want to have these
+ directories outside of your web tree.
+
+ The data directory is used for storing user preferences, like
+ signature, name and theme. When unpacking the sources this directory
+ is created as data/ in you SquirrelMail directory. This directory
+ must be writable by the webserver. If your webserver is running as
+ the user nobody you can fix this by running: