![]() Unpack the files in the /var/www directory and if you are using other the use the other directory. %2Fsquirrelmail%2Fsquirrelmail-1.4.21.tar.gz Remove the squirrel mail that on your system.ĭownload the original current version of squirrelmail from here: In the log it seems fine so use my first advice. I also saw on the squirrel mail page something about absolute paths, but I couldn't find anything in the file pointing to /var/lib/squirrelmail/data folder. rw- 1 www-data www-data 108 13:23 there be something in Apache that is wrong? I did find an old post saying something about a safe mode but I can't find anything in the Apache directory relating to safe mode. I've also done chmod 777 -R but that didn't work either.ĭrwxrwxrwx 2 www-data www-data 4096 13:23. This is what the data folder looks like right now. ![]() Wouldn't both be using the same Apache configuration files? I don't really understand the different permissions between using the IP address and the. I have done chown www-data to the data folder and chmod 777, still not able to log in. To work around this, edit src/ still have not been able to solve this, I'm not sure what I'm looking for in the file but in the config.php the $data_dir is /var/lib/squirrelmail/data. For some reason, the session id isn't retrieved properly when redirect.php sends to location.php. You'll need to patch the source code for this to work. Note: One user claims the following when using SquirrelMail 1.5.1 or later, but because the 1.5.x series is a development branch, this is likely to change significantly, so this information may be out of date: Now, wherever your tag is, this is what you want (notice this also includes SquirrelMail's JavaScript auto-detect code):\n Īnd the actual input fields would be as such:\n If you still have problems, please look at the plugin code or ask for help on the SquirrelMail plugins mailing list.Īt the very top of the file, insert this:\n Īnd in the, insert this (this is just the auto-focus for the cursor):\n ![]() Below is a sample from a working installation where the relevant login plugin hook is called, which might even make this compatible with ANY plugins that use the same hook as well as password_forget. Ideally, you'd need your custom login page to be a PHP file that can make the correct function call into that plugin. If you are using the password_forget plugin, more work is required to build the login form correctly. You don't have to add all hooks used by all plugins, only the ones affecting the login process. ![]() ![]() View the plugin's setup.php file to find out which ones those are, then look at where those plugin hooks are used in src/login.php, and add them accordingly to your custom login page. In addition to the above, your code needs to execute any and all SquirrelMail plugin hooks used by any login plugin you are trying to get working. Don't forget to destroy SquirrelMail sessions first, otherwise if a user didn't logout properly, there's a risk of mixing personal information. Put this in the body tag so SquirrelMail housekeeping can be executed when the page loads:\n Īlso note that you may or may not want to use HTTPS instead of HTTP for secure password transmission. Here is a sample of the required HTML code (obviously, you need to add your own layout code):\n It is easy to put username and password input fields in any web page and let the user log into their SquirrelMail without going to the default SquirrelMail login page. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |