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.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.
...
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.
...
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 MB (10GB). Please note that the context quota is used for PIM attachments, signatures, vcards, etc. More details can be found here. It's not the summary of each existing single mailbox.
...