Tag: Cpanel Hosting

Recently cPanel made an announcement on their official blog about deprecation of Squirrelmail as a webmail option in cPanel.

As of cPanel & WHM version 74, cpanel will begin to deprecate support of SquirrelMail and stop shipping SquirrelMail for new installations of cPanel & WHM in version 76 followed by removing their support with version 78.

The news may come as a shock to many people who are used and habitual to use Squirrelmail as webmail option. Squirrelmail has been favourite webmail for years due to its simplicity and ease of managing emails using webmail.

But it seems, there has not been much progress in development of Squirrelmail which has forced cPanel to stop offering squirrelmail as an option. As per the official blog post from cPanel website,

SquirrelMail’s last update was May 30th, 2013, with their last release on July 12, 2011. In that seven years, 4 versions of PHP have reached End of Life, and we have worked with others in the community to maintain SquirrelMail. Unfortunately, recent security patches have significant problems, forcing us into a choice. Exclude the security fix and ship SquirrelMail with known security flaws, ship a secure version with known interface issues, or attempt to fix the problems.

Webmail users now expect a better experience than SquirrelMail provides. Rather than continuing to ship an unmaintained application, we decided to remove SquirrelMail.

While we can certainly understand cPanel’s concern from security point of view, it would have been really helpful if Squirrelmail was able to cope up with developments and upgrades.

Following the removal of Squirrelmail eventually with release of cPanel version 78, WebHostUK will also stop offering SquirrelMail as a webmail option on our cPanel hosting servers. We urge our customers, who are using Squirrelmail, to consider using other alternative webmail options such as Horde or Roundcube and export any address book they may have under Squirrelmail.

If your mailbox that is always going over-quota or filling up with mail like your default account or your spam box and you don’t want to have to keep logging in and deleting the emails manually below you can find the steps how to auto delete the emails.

Log on to your cPanel Interface.

Go to ”Advanced‘ section.

Click on “Cron Jobs“.

Select the specific time from the lists provided.

You should enter the command to run in the “Command” field.

Note: You should make sure to enter the proper command and the full path to the file.

Hit the Commit Changes button and wait until sometime after 6:45 AM (assuming you set it up to run at that time) and login to your default email account to see if your emails have been deleted

If everything looks good your default inbox will now have any emails that are older than 10 days automatically deleted

To login into your default email account you use your cpanel username and password

If you wanted to have all the emails deleted that are older than three days you would simply change the –days option to 3

If you wanted to have all emails inside your mail directory including sent mail, spam, etc. that are older than 30 days deleted…
/usr/bin/archivemail –quiet –delete –days 30 /home/{USER}/mail/*

If you had an email account named info @ yourdomain.com and wanted to have all the emails in that inbox that are older than seven days deleted…
/usr/bin/archivemail –quiet –delete –days 7 /home/{USER}/mail/{yourdomain.com}/info/inbox

If you had an email account named info @ yourdomain.com and wanted to have all the emails in your sent-mail folder that are older than twenty-one days deleted…
/usr/bin/archivemail –quiet –delete –days 21 /home/{USER}/mail/{yourdomain.com}/info/sent-mail

Don’t forget to change {yourdomain.com} to your actual domain name !

You can look in your mail directory via your ftp client or the online file manager to see where your mailboxes are located.

NOTE: We *CANNOT* recover mail deleted in this manner, so please use this tutorial at your own risk

cPanel continues to surprise the industry-releasing one new feature here and there, making sure that its clients get the most out of their investments. With its newest innovation, cPanel is set to enhance the client’s web hosting experience.

The launch of EasyApache 4 (EA 4) brings various improvements in installation, update, and other features that are important for the client. EasyApache 4 is a major revamp of how cPanel and WHM ships and maintains the Apache and PHP distribution.

EasyApache 4 represents a total overhaul of how cPanel & WHM ships and maintains our Apache and PHP distribution.

Simply explained, EasyApache is the software that installs, configures, updates, and validates your web server, PHP, and other components of your web server.

cPanel & WHM installs EasyApache 4 by default on new installations of systems that run cPanel & WHM version 58 or higher.

EasyApache 4 offers the following improvements over EasyApache 3:

Binary packages

Software collections

Path reorganization

MultiPHP support

Post-update actions

Binary packages

Binaries are cost-efficient improvements that save time and monetary resources for site owners, server owners, and developers.

Rather than compile binaries from source, we build RPM packages with binaries that you can easily install via yum. This allows for quicker, automatic updates of packages.

The system forks any custom packages from the Red Hat® specification files, but contain the latest version. Binary packages also allow Apache and PHP to automatically update.

Binary Packages allow for quicker updates, installations, and the ability to spin down and spin up different web stacks and configurations quickly. This reduces the cost for site owners and server owners.

These binaries reduce the time it takes for updates and installs to a few minutes. This also allows developers to quickly spin up and spin down different configurations.

Software collections

EasyApache 4 uses the Software Collections Library (SCL) for PHP packages. The use of SCLs enables the installation of multiple, concurrent version of PHP on the file system.

An SCL is an alternate path inside the /opt file that contains the full file system that various software needs. When you enable an SCL, it adds the path within that environment to the system. Commands that do not specify a path and scripts that use the /usr/bin/env file to determine their path can then use this path to find the appropriate version of the software.

How to execute a script with SCL

To execute a script with a software collection environment, you must run the scl command. For example, to run the php-v command on a php56 collection, run the following command:

This directory contains all the logs for the apache2 file as well as all access logs.

/etc/apache2/

This directory contains the configuration directory for Apache and contains all directories for Apache includes, modules, and configuration files. This directory does not contain log files.Note: This directory uses the symlink to the usr/lib64/apache24/ directory.

/usr/lib64/apache2/modules/

This directory contains all of the dynamic modules for Apache.

/opt/cpanel/ea-php*/

This SCL directory contains all of Apache’s binary files.

/etc/apache2/logs/access_log/

This file contains HTTP requests that the server received and that did not go to a domain.

/etc/apache2/logs/domlogs/

This directory contains a log of HTTP requests that the system routed to a domain.

/etc/apache2/logs/error_log/

This file contains error information.

/var/www/html/

This directory contains the document root for the server. It contains default pages that users can see.

/etc/apache2/logs/

This directory contains an alias to the /var/log/apache2/ directory.

/etc/apache2/modules/

This directory contains an alias to the /usr/lib64/apache2/modules/ directory.

MultiPHP support

EasyApache 4 supports multiple versions of PHP. Multiple PHP versions allow you to assign different PHP versions to each of your domains. Coupled with automatic upgrades, this ensures that your PHP applications run on the most up-to-date, secured PHP versions.

Post-update actions

EasyApache 4 removed OptMods and no longer supports them. However, in addition to the new RPM actions that EasyApache 4 can execute from its specification file, we created yum-plugin-universal hooks. These new hooks allow for executable actions based on the package name they operate in. For example, if you run a script on an ea-* package, if any updated packages exist in the ea4 namespace, the system executes these scripts.