On our Managed Servers you have the possibility to have a daily, weekly or monthly overview of all mails that are currently in your spam folder sent to you. All you have to do is to set the interval for a mailbox in the “Spam Report” tab.

This function is especially suitable for customers who retrieve their mails via POP3 and have spam moved to a separate folder, because via POP3 only the inbox is retrieved.

To move a spam mail to the Inbox (to read it via POP3 or because it is not spam), you have two options:

  • in the mail with the spam report you will find a link
  • in ISPConfig you can select every single mail and have it moved to your inbox

Note that some email programs have their own spam policies and may move a mail back into the spam folder themselves.


Using the search field you can filter individual mails, whereby the search value extends over all values.

Empty trash and spam automatically


Did you know that on our managed servers you can empty the trash and the spam folder automatically?

Just open the mailbox in ISPConfig and then you can set the duration how long mails should stay in the trash or in the spam folder under Mail Filter.

Set Staging Environment


If you want to make an update or adjustments to your website or shop, you can also test this in a staging environment, so that it won’t affect the live site if something goes wrong.

Individual Content Management Systems

Most CMSs allow a staging environment to be set up easily if a few data are set accordingly. For the following CMS this works fully automatically:

  • Joomla
  • Typo3
  • Magento 2
  • Shopware 5
  • Shopware 6
  • WordPress

If you are missing a CMS in the list, we are happy to implement it.

Set up staging environment

Open the website in ISPConfig and go to the tab “Staging”.

Under “Advanced” you can set further values:

Hostname for Staging – If you enter your domain and you enter staging here, then the staging environment will be accessible at

Username and Password – To secure the staging environment, you can enter a username and password here to access the staging environment.

To set up a staging environment, simply enable “Create Staging Now” and click “Save”. This will copy the complete website and the selected database and adjust the clones accordingly.

Access Staging Environment

Once the creation is complete, you can access the staging environment in the browser. If you have not specified a hostname, the URL is e.g. If you have specified a hostname, the URL is e.g.

Configure PHP memory limit


Before we show you how you can individually set the PHP memory limit per customer and website on our full-managed servers, first a few informations:

Why do I need a PHP memory limit at all?

PHP always reserves a part of the RAM for executing scripts. How much RAM can be reserved for this is defined with the PHP memory limit.
If there would be no limit, a bad script could cause the memory to fill up slowly but surely, so that the speed of the web pages becomes much slower and in the end even the whole server can become unstable.

How high should the PHP memory limit be?

Unfortunately it is not possible to give a general answer.

It depends on which CMS you use and how many applications you have installed there. The values vary from 32 MB for a simple WordPress installation up to 512 MB for a complex shopware installation

For this reason we do not set such a high limit, so that any kind of CMS can get along with it (WordPress needs less than shopware).

Setting the PHP memory limit for a website

If you open the settings of a website ( similarly of course also for sub vhost and alias domain vhost), you can set the limit directly.

If you enter a 0 here, the limit is automatically set to the value of the server or to the value of the used webserver configuration, if you have also defined PHP settings here.

Please note that the “Individual php.ini settings” always have priority. If you have entered a different limit there, this value will be taken as long as it is not greater than the defined limit. The same applies to a memory limit that you have set in the direct (web server configuration).

Setting the PHP memory limit for a client

If you don’t want your customers to enter arbitrarily high values for their websites, you can also assign a limit to each customer. This limit behaves in the same way as the website memory limit: the customer can distribute “his” limit to all pages individually.


Set the compression for web pages


In the following we show you how you can set the compression of a website on our fully managed servers.

There are several options available to you:

  • Disabled
  • Gzip
  • Brotli
  • Brotli + Gzip

Compression with Brotli + Gzip is the default setting to compress smaller files directly when the website is delivered.Brotli is a newer type of compression developed by Google as an alternative to Gzip, Zopfli and Deflate. Google’s case study of Brotli has shown that the compression rates are up to 26% lower than other compressions and the CPU usage is also lower.
The server and the browser (visitor) must be compatible to Brotli and use an encrypted connection via https to benefit from compression.

If your website is delivered with Brotli compression, you can test on here.

You can see the compression levels of Gzip and Brotli for example here.

Set minimum TLS version


You can set the minimum TLS version for each website on our fully managed servers.

Various vulnerabilities have led to experts recommending long ago to disable all versions of SSL and TLS 1.0 (this has always been the default setting on our servers). Meanwhile, websites should no longer be reachable with TSL 1.1, but at least support TLS 1.2.

To set the minimum TLS version, you just have to go to ISPConfig and select the “Minimum TLS version”:


Every modern browser supports TLS v1.2, most also TLS v1.3, but since the latter version is still considered experimental, it is a good idea to set the pages to TLS v1.2. If you want to be absolutely sure that your site can be reached with an outdated browser, you must choose TLS v1.1.

To test the SSL settings of your site, you can use one of the two links:

Backup-Now for websites and database with ISPConfig


You can have automatic backups created on our fully managed servers. Now you also have the possibility to manually trigger a backup of a website or a database.


You can use it, for example, to back up the database before you make major changes to your project. If something goes wrong, you can restore the freshly created backup.

When you start a manual backup, the oldest backup is deleted afterwards.

Configuring Backups in ISPConfig

You can find the settings for the backups in the Backups tab of your website.

You can set the number of backups to be saved under “Number of backups” between 1 and 10.

You can set the interval to different values:

  • Automatic backups inactive
  • Daily
  • Weekly (every Sunday)
  • Monthly (on the 1st of each month)

If you choose “Automatic Backups inactive”, only manual backups are created via Backup-Now.

Start Backup-Now

To start a manual backup, you just have to click on the button “Backup website now” or “Backup database now” to switch from grey to blue and then save the settings:


Until a backup is complete, you cannot trigger another manual backup:

After the backup is complete, you will find the backup as usual under “Existing Backups”.

By the way, you can recognize a backup created by Backup-Now by -manual in its name.


Datalog History


On our Managed Mail Servers and the Full-Managed Servers you can track and undo changes made in ISPConfig.

However, only the settings are written back and not the contents of websites or similar. For example, if you have deleted a website you can only restore the “basic structure” – the contents of the website have to be restored from backups.

Show Datalog History

You will find the menu item “Show Datalog History” under “Monitor”.


The history then looks something like this:

When you select an entry, the corresponding activities are displayed and you have the possibility to undo the change:



Enhanced spam check for mailboxes


On our managed mail servers and full-managed servers you can not only set greylistening for each mailbox to on and off for the spam check, but also for RBL, SPF and spoofing.

SPF and RBL are automatically activated for new mailboxes, greylistening and spoofing are disabled by default.

What do these spam checks do in detail?


The owner of a domain can specify which servers are allowed to send mails. If delivery via another server is attempted, the mail can be rejected directly. This happens in particular with spam mails if the sender in a mail is forged. Unfortunately, there are also postmasters who define these specifications incorrectly or simply forget to add a new server.

It can also lead to problems with the SPF check if mails are sent via an external mail gateway beforehand.


Our mail servers check incoming mail across one or more lists of servers that have recently sent spam. Connections from “spam spinners” are rejected directly.


At the first connection the sending mail server gets a message that it should try again in a few minutes. This can reduce spam, but is not always optimal for mailboxes that are used for direct communication with customers. Otherwise it can happen that the customer sends a mail and then you have to explain that the reception can take up to 5 minutes.

If a mail server has passed the other checks on the second attempt, its IP is on a whitelist and mails sent later arrive without greylistening.


Email spoofing refers to the forgery of the email header so that the message gives the impression that it has a different origin or source. Spam distributors often use spoofing to get the recipients of the email to open the message so that they respond to its content.

Set individual checks

Log on to your server in ISPConfig and select the mailbox for which you want to customize the SPF, spoofing, or RBL check.


Monitor your server


You always have full access to the monitoring of your managed server and can view the data directly in your browser, via your smartphone or an add-on from Firefox / Chrome.

Depending on the monitoring value there are two limit values Warn and Crit. If yours is exceeded, the display changes to orange (Warn) or red (Crit). You can adjust the limits directly in ISPConfig on your managed server..

If the state changes, you will receive a mail after a certain time. You will get the notification if the status changes to OK, Warn or Crit.


Set limit values


Log into ISPConfig on your Managed Server and open the “Tools” in the upper right corner. Under Managed Server on the left side you can set the monitoring.

To adjust the values, select one of the checks and then define the limits. For the mail queue it looks like this:

If there are 20 to 29 mails not yet sent on your server, the status changes to Warning. If 30 or more mails have not yet been sent, the status changes to Critical.



Just open the URL for monitoring in your browser and log in with your access data.

Smartphone APPs

aNag for Android


Grab aNag from the the playstore and start the App.

You can freely choose the name – it only serves to distinguish between different instances.

The other data are:
Instance type: Icinga/Nagios (HTML)
Username: Your Username
Password: Your Password

easyNag for iPhone & iPad


You can download and install easyNag here.

You can use the settings for Android for the individual values.

Add-On for Firefox and Chrome

For Firefox you can use the current version of imoin.



Install the add-on in Firefox via Add-Ons or in Chrome via this Link and set up access:

Version: Nagios Core 4.0.7+
Username: Your Username
Password: Your Passwort