Below you can find a history of recent module versions as well as the latest one. There is also a change log with information of the current version.
| Table of Contents |
|---|
V 1.0.46
| Status | ||||||
|---|---|---|---|---|---|---|
|
As of this version it's now possible to setup different quota values for product even those are in the same setup.
In the module setup are now different new fields to define the quota for a product:
Also a new checkbox named "Hide Configurable Options for Mailboxes Other Than the Selected Product" got added, as shown in the example screenshot below:
When this checkbox is selected, the Configurable Options (acc_limit_productivity, acc_limit_secure, and acc_limit_productivity_secure) will be hidden during the product ordering process. However, after the product has been ordered, it will still be possible to update the configurable options and purchase the ability to create mailboxes of other types.
V 1.0.45
| Status | ||||||
|---|---|---|---|---|---|---|
|
In this version the "Email Forwarder" function got optimized. It now possible to add up to 10 internal and/or 1 external address as recipients for a forward address.
The recipients field got changed to a text area field, all recipients must be entered as comma separated.
Additional to that you can now also edit the already existing forwarder recipients with the new button.
As soon as you confirm your new edited recipients, the module deletes the existing forward and creates a new one with the new values. Please note here as well, entries need to be comma separated.
Important additional note: After clicking the "Confirm" button, 2 API call are fired. The 1st deletes the whole existing forwarder and the 2nd creates a new one the the new recipients. In case the recipient entry list is invalid (for example not comma separated), you'll loose the existing forwarder! It can be re-created afterwards but it's important to provide a valid entry here
Please note: In the edit mode you can just edit the recipients but not the forwarder address itself. If you want another (additional) address please create a new one and/or delete the old one.
V 1.0.44
| Status | ||||||
|---|---|---|---|---|---|---|
|
As of this version it's possible to set a so called "Soft Delete" for mailboxes. That means, in case a mailbox get deleted in the client area, you can set a value of days for the final delete of the affected mailbox(es).
Please see the description below, how to setup and use.
First of all it's huge important to setup WHMCS's cron jobs properly as the system use this to execute the final deletion of a mailbox. To check if cronjobs are setup, please have a look into the "Automation Status" top right in the Admin Area. Next, top left you can see the cron status. It should look similar to this, depending on your config:
If you see any not working cron item, please take care to solve the error before using this version. Otherwise the final deletion of a mailbox won't work.
To setup your products to use this feature, please edit all your products and set the "Default Deletion in Days" field to a value that fits as default for you. The final value can later adjusted by the mailbox admin in the Client Area.
Please note (this is huge important):
You need to save at least one of your product, even you do not want to setup a default value for "Default Deletion in Days". Otherwise the responsible database table does not get created!
In the Client Area it's now possible to click on the "Delete" button as usual. Now there will be a new popup window to define the final delete of a mailbox. The default value here is what you have set in the Admin Area before.
If you have no default value set, it's always "0" days. Important: "0" days means, the mailbox get deleted immediately.
After confirmation you'll see the affected mailbox in the list marked as strikethrough as in the example below.
You'll also have a new entry on the left for the overview of all marked mailboxes for the final deletion.
Please note:
All mailboxes marked as "Soft Delete" get removed the permission by an API call with the following body parameter:
| Code Block |
|---|
{
"send": false,
"receive": false,
"maillogin": false,
"weblogin": false
} |
The mailbox admin has also the option to remove the "Soft Delete" again, for sure only if the mailbox got not deleted finally. To do, just click the "trash" icon in the overview below and confirm.
After that, the permission are granted again.
Final note about the execution time of the mailbox delete via cron:
The cron job currently operates with day-level precision. For example, if a client creates a mailbox deletion request on 20.05.2026 and specifies that the mailbox should be permanently deleted after one day, the hook will delete the mailbox on 21.05.2026 immediately after the WHMCS daily cron job has finished running.
Therefore it's huge important to setup cronjobs as described above. The cronjob settings you can find in the Admin Area in "Settings" > "Automation Settings"
}
V 1.0.43
| Status | ||||
|---|---|---|---|---|
|
The option "Allow To Change Password" when creating a product get now included within the responsible API call when creating or changing a mailbox.
V 1.0.42
| Status | ||||
|---|---|---|---|---|
|
The calculation of the available pool quota was misleading. Older mailbox without unified quota were not included in the leftover calculation. This got fixed.
V 1.0.41
| Status | ||||
|---|---|---|---|---|
|
Some minor fixes.
- In the product settings it was possible to set the amount of aliases. The mouseover of the question mark displays a maximum of 50 aliases, that's correct.
This is now limited to 50 strictly even more are setup. - In the product setup it's now possible to enable/disable the "Catch All" option in the client area by using a simple switch.
- In the client area you can find now the "Pool quota setup in product definition as well as the leftover possible amount of storage to use vs the total storage.
V 1.0.40
| Status | ||||
|---|---|---|---|---|
|
It's no longer possible to create a context with the module if the context name, generated by the module, is already existing in the WHMCS database.
...
After a checkout in the order process is done and the context already exist, an appropriate error message is thrown to the customer.
V 1.0.39
| Status | ||||
|---|---|---|---|---|
|
The context quota get set fixed to 10240 MG MB (10GB). Please note that the context quota is used for file sharing, global address book, etcPIM attachments, signatures, vcards, etc. More details can be found here. It's not the summary of each existing single mailbox.
The mailbox quota is set as unified quota, valid for mail and drive (documents as well, if activated)Mail and Drive.
With this version you can now also set an unlimited value for allowed services in a product. The value "-1" is used for such an unlimited service.
V 1.0.39
In this version you can now use punny code by creating a mailbox. In the client area where all existing mailboxes are listed, you'll find the names in clear text (translated from punny code). It's just by creating a mailbox.
| Attachments | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|