[EMAIL PROTECTED] said: >> Chris Hilts said: >>>> I was wondering if someone can shed some light on a question that I >>>> have. >>>> What is the purpose of the /var/spool/squirrelmail/attach directory >>>> and >>> <SNIP> >>>> dating >>>> back from a few weeks ago. Is there any reason I shouldn't delete >> these >>>> files? >>> >>> It is the location where attachments are temporarily stored during >> compose >>> sessions. If the compose times out, occasionally an attachment will be >> left behind "unclaimed". Yes, you can safely delete older files in this >> directory. Most of us run a cron job (tmpreaper works like a charm for >> me) which automatically deletes files over a certain age. >>> >> >> If you can't setup a Cron Job to do it for you (because of payed >> hosting, >> ect...) you can tryout a plugin which I wrote a while back, just never >> released. >> >> When someone logins in, it checks the attachment directory for files >> over >> 1 day old (will be configurable later) and deletes them. It also >> supports >> having your data directory and your attachment directory the same, as it >> skips over any php files, the default_pref, address books, ect... There >> may have been a few I missed that it shouldn't delete, so backup your >> data >> directory first! (But in your case, your data and attachment >> directories >> are different so it doesn't matter) > > Just a note: we typically recommend you do NOT give your web server READ > access to the attachments directory (only WRITE access), but to get this > plugin to work, you'll need to give your web server READ access to that > directory (if you do so, make sure you put a "deny from all" .htaccess > file in that directory). If you have the right access (or your hosting > provider will help), you will be best off doing this as a cron job). > > (Jimmy, you may want to add that info to the plugin README) > > - Paul
I will definitely put that in the readme, I will also recommend not putting the attachments directory (or even the data directory) in the web server root, if at all possible, and if you have to, then add an .htaccess file to the directory to restrict access. This plugin should only be used as a last resort if you don't have access to make a cron job. I should also probably provide a few examples on how to do the cron job just to make it that much easier. Thanks and I'll get the recommendations in there. Jimmy ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
