Retention policies need some rework.

Currently if you set up a new retention policy, it uses the time that the policy was created/run as the start date for counting the days till deletion. Meaning setting up a 5 year policy will not delete emails in stores that are older than 5 years, it will wait 5 years from the day it was run to delete them. If you ever need to change a long retention policy or add a new one, it simply isn't going to function correctly on existing databases.

Additionally, the condition requirements are mediocre. Why is there no option to not have any condition and simply have a global retention policy? There isn't an option for folder/user/group based retention, nor an option to set conditions using anything other than AND operaters between conditions.

Suppress "Backend Database Error" Warning when OS is rebooted

We reboot the Mail Archiver server weekly and after installing Microsoft Updates, which can often result in an email warning being sent out with the subject "GFI Archiver: Backend Database Error" and the body:

"GFI Archiver failed to archive any emails into the backend database.

The following error message was reported:
The transaction has aborted.

Regards,
GFI Archiver

We do want to be notified in all other cases if there should be an issue, but rebooting is not one of them. A workaround is to disable all such warning messages (option found in Configuration > general settings > additional settings > send archiving status notification), but then we are not notified of other potential problems.

I did file case GFI-160525-412152 on this. It was suggested to me that I post this in the ideas area.