This article aims to explain how WHM and cPanel version 11.44 and it’s previous versions make updates to SquirrelMail web application along with a guideline for users to make customizations to the installation.
It is necessary to understand how WHM and cPanel update SquirrelMail before making changes to your SquirrelMail installation.
A custom SquirrelMail tarball can be created. Necessary factors are:
During its runtime, /usr/local/cpanel/bin/update-squirrelmail looks for SquirrelMail custom tarballs. The value of $sqversion in these locations should match the value of $sqversion that the script defines. Its is important for the tarballs to extract to usr/local/cpanel/base/3rdparty/squirrelmail directory.
Certain characteristics, including themes, graphics, and plugins of SquirrelMail, can be customized using the overlay tarball. However, there is no necessity for the overlay to contain complete SquirrelMail distribution. Only the contents that you wish to modify are enough as cPanel and WHM overlay it onto the SquirrelMail installation. The chosen tarball needs to be installed and extracted while the /usr/local/cpanel/bin/update-squirrelmail script looks for appropriate files.
In case of multiple tarball files, the script uses them in the order in which it is listed.
Follow the given steps to install SquirrelMail plugins.
Installed Plugins 1. Login Authentication (login_auth) 3.0 Available Plugins: 2. administrator 3. Bug Report (bug_report) CORE 4. calendar 5. change_password 0.2 6. Demo (demo) CORE 7. filters 8. fortune 9. info 10. listcommands 11. mail_fetch 12. message_details 13. New Mail (newmail) CORE 14. Preview Pane (preview_pane) 2.0 15. sent_subfolders 16. spamcop 17. squirrelspell 0.5 18. Test (test) CORE 19. translate
To take a look at your new SquirrelMail configuration, go to example.com/sessionid/3rdparty/SquirrelMail/src/configtest.php where example.com denotes your domain name and session is indicates your present security token.