This document explains how cPanel & WHM versions 11.44 and earlier update the SquirrelMail webmail application, and how you can customize your SquirrelMail installation.
- As of cPanel & WHM version 56, SquirrelMail ships as an RPM. To customize your SquirrelMail RPM, follow the directions in the How to Build and Install Custom RPMs documentation.
- Customization of SquirrelMail gives you full control over the end user experience. However, cPanel Inc. does not support these customizations.
General installation procedure
Before you customize your SquirrelMail installation, it is useful to understand how cPanel & WHM updates SquirrelMail.
/scripts/upcpscript runs to update cPanel & WHM.
- It also executes the
/usr/local/cpanel/install/webmailscript then executes the
/usr/local/cpanel/bin/update-squirrelmail script performs the following actions:
It uses the following command to remove the current SquirrelMail installation:
It extracts the appropriate SquirrelMail source tarball to the
For more information, read the Where to place a custom SquirrelMail tarball section below.
- It changes the ownership of the SquirrelMail installation to the
rootuser and the
- It changes the SquirrelMail data directory's permissions to
It checks for the existence of the
For more information, read the Prevent changes to the SquirrelMail configuration files section below.
- It extracts IMAP configuration values and copies them into place.
Prevent changes to the SquirrelMail configuration files
During Step 5 of the installation procedure, the
/usr/local/cpanel/bin/update-squirrelmail script checks for the existence of the
If that file exists and is executable, the
/usr/local/cpanel/bin/update-squirrelmailscript executes it and terminates.
- This bypasses cPanel & WHM's manipulation of the SquirrelMail configuration files.
- Step 6 of the installation procedure does not occur.
- If the
/var/cpanel/squirrelmail/installfile exists but is not executable, the file contents print to
STDOUTand the normal cPanel & WHM configuration of SquirrelMail continues for the remaining steps.
There are several ways to customize the SquirrelMail installation.
For instructions on how to create a custom SquirrelMail tarball, read the SquirrelMail documentation.
For more information about how to place a custom SquirrelMail tarball, read the following non-sequential steps:
/usr/local/cpanel/bin/update-squirrelmailscript runs, it checks for custom SquirrelMail tarballs. The following table lists the locations it checks:
Use this location for a compressed tarball that you want to apply to a specific SquirrelMail version.
Use this location for an uncompressed tarball that you want to apply to a specific SquirrelMail version.
Use this location for a compressed tarball that you want to apply to SquirrelMail regardless of version.
Use this location for an uncompressed tarball that you want to apply to SquirrelMail regardless of version.
If any of those tarballs exist, the
/usr/local/cpanel/bin/update-squirrelmailscript uses that tarball instead of the cPanel-supplied tarball. cPanel & WHM uses the locations in the above list in the listed order.
For example, if the following statements are true, cPanel & WHM uses the
- Both the
/var/cpanel/squirrelmail/squirrelmail-1.49a-local.tar.gzfile's version number is specified in the
- Both the
The value that
$sqversionrepresents in these locations must match the
sqversionvariable that the
For example, if the
sqversionparameter is set to the
1.49aversion in the
/usr/local/cpanel/bin/update-squirrelmailscript, save your custom tarball as the
These tarballs must extract to the
Where to place a custom overlay file
For more information about how to place a custom overlay file, read the following non-sequential steps:
The overlay tarball allows you to customize specific aspects of SquirrelMail.
For example, you can use an overlay to change graphics, themes, or plugins.
The overlay does not need to contain a complete SquirrelMail distribution. It only needs to contain the components that you wish to modify, because cPanel & WHM overlays it onto the SquirrelMail installation.
For example, it can contain one image file.
However, it must contain a directory structure that mimics the structure of the
/usr/local/cpanel/base/3rdparty/squirrelmaildirectory, but that starts with
Once you determine which tarball to use for the source install and extract it, the
/usr/local/cpanel/bin/update-squirrelmailscript checks for the following files:
Use this location for a compressed overlay you want to apply to a specific SquirrelMail version.
Use this location for an uncompressed overlay you want to apply to a specific SquirrelMail version.
Use this location for a compressed overlay you want to apply to SquirrelMail regardless of version.
Use this location for an uncompressed overlay you want to apply to SquirrelMail regardless of version.
As with the custom SquirrelMail tarballs above, the following statements are true:
- If the script locates multiple tarballs, it will use them in the order that is listed above.
- The value of the
$sqversionvariable must match the version number that the
Install SquirrellMail plugins
To enable a SquirrelMail plugin, perform the following steps:
- Run the
/usr/local/cpanel/base/3rdparty/squirrelmail/config/conf.plcommand to open the SquirrelMail Configuration menu.
Enter the number of the
Pluginsoption . The code block below lists the available SquirrelMail plugins that appear:
- Enter the number of the Plugin that you wish to install.
- Save your changes and exit the SquirrelMail Configuration menu.
To test your new SquirrelMail configuration, navigate to
example.com represents your domain name, and
sessionid represents your current security token
Before you run the configuration test for SquirrelMail from a remote server, you must add the following line to the