X-Git-Url: https://vcs.fsf.org/?p=squirrelmail.git;a=blobdiff_plain;f=INSTALL;h=3cdd419d6874c8fe65ef538ac2f554aa044e549a;hp=58582b33108a9d4db7d16e5135c46ef7e0f6a63d;hb=09e47788e94cc1dee1b8deec4dc7c6435f50b9eb;hpb=b731cd834272ca2b8e2798c451c636be5545bada

diff --git a/INSTALL b/INSTALL
index 58582b33..3cdd419d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -22,7 +22,7 @@ Table of Contents:
 
   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
+  PHP4 v4.0.2. If you need to upgrade please go ahead and install the
   latest release version of PHP4.
 
 a. Obtaining and compiling PHP4
@@ -58,6 +58,8 @@ b. Changing php.ini
   be sure to change the session.save_path to someplace that can only 
   be read and written to by the webserver.  session.save_path is the
   location that PHP's session data will be written to.
+  
+  Squirrelmail 1.2.x also requires register_globals to be enabled. 
 
   SECURITY WARNING - If a user has access to write PHP scripts on your 
   system and knows the location where PHP stores session data, he 
@@ -65,6 +67,10 @@ b. Changing php.ini
   session's data with his own PHP script.  Caution should be used when 
   setting up permissions and locations of php.ini and the session data.
 
+  FILE UPLOADS - Note that sending messages will not work if your
+  "file_uploads" setting is "Off". Squirrelmail requires that setting
+  enabled in order to work.
+
 c. Setting up .php files to use PHP4
 
   You need to create a .htaccess file in you SquirrelMail directory
@@ -118,7 +124,12 @@ b. Setting up directories
 
     $ chown -R nobody data
     $ chgrp -R nobody data
-  
+
+  Keep in mind that with different installations, the web server could
+  typically run as userid/groupid of nobody/nobody, nobody/nogroup, 
+  apache/apache or www-data/www-data.  The best way to find out is to read 
+  the web server's configuration file.
+
   There also needs to be a directory where attachments are stored
   before they are sent. Since personal mail is stored in this
   directory you might want to be a bit careful about how you set it
@@ -137,14 +148,30 @@ b. Setting up directories
   not supposed to read change the last line to chmod 777 SomeDirectory
   or simply use /tmp as you attachments directory. 
   
-  If a user is aborting a mail but has uploaded som attachments to it 
+  If a user is aborting a mail but has uploaded some attachments to it 
   the files will be lying around in this directory forever if you do not 
   remove them.  To fix this, it is recommended to create a cron job that
   deletes everything in the attachment directory.  Something similar
-  to the folling will be good enough:
+  to the following will be good enough:
 
     $ cd /var/attach/directory
     $ rm -f *
+    
+  However, this will delete attachments that are currently in use by people
+  sending email when the cron job runs.  You can either (1) make sure that
+  the cron job runs at an obscure hour and hope that nobody gets upset, or
+  (2) you can run a modified version of the commands above.  Check out the
+  man pages for other commands such as 'find' or 'tmpreaper'.
+  
+  One sample script you could set up that would erase all attachments, but
+  wouldn't erase preferences, address books, or the like (just in case your
+  attachment directory is the same as your data directory) might look like 
+  this:
+   
+    $ rm `find /var/attach/directory -atime +2 | grep -v "\." | grep -v _`
+    
+  Remember to be careful with whatever method you do use, and to test out
+  the command before it potentially wipes out everyone's preferences.
 
 c. Setting up SquirrelMail
 
@@ -163,7 +190,7 @@ c. Setting up SquirrelMail
   possible example of this is: 
      http://www.yourdomain.com/squirrelmail
      
-  It should be pretty stright forward to use. Some more documentation
+  It should be pretty straight forward to use. Some more documentation
   might show up one day or another.