In the last version of Cleanmail we developed a first milestone of the feature.
However, this was announced with several warnings:
In this release we provide answers to these issues, making this feature more stable.
To prevent remediation errors, before deleting a message on the remote platform, it is retrieved and stored in the user's quarantine. This allows to have quarantine features available on these messages (viewing, analyzing, quarantine reporting, and releasing).
Note that a remedied message cannot be released by the end user; only an administrator can do so. If quarantine is not enabled for the user, no storage occurs, and the remedied email is deleted permanently.
To enable bulk remediation and avoid potential errors with the mail server (as limit rate), remediation tasks are queued. This means they are not executed immediately. In case of error, several attempts ill be made.
The log interface has been redesigned to clearly display the progress status of these tasks. A “Remediation” tab has been added for easier access to this information, although, as a reminder, it is also possible to use a "Action is Remediated" filter.
Based on the model of the remediation, the action of releasing a message is now an asynchronous action. A positive response to this request indicates that the action has been accepted, but not that the message was successfuly sent. The log and quarantine interface have been reworked to track the progress of the current request (in progress, success, error).