GFI Archiver can also be used with other email servers and can poll email from any mail server that supports IMAP and Active Directory.

In my case I am using GFI Archiver Database.Īrchiving Methods: This wizard provides an administrator to select the archiving methods as below: For evaluation purposes of 25 or less users, GFI Archiver contains a free database called Firebird. GFI Archiver stores only metadata and email headers in the SQL database, the raw email data is stored encrypted and compressed on disk. Most of the deployments use a Microsoft SQL Server (2005 or later) database. Licensing: Provide the License key and continue.Īrchive Store Settings: This wizard will allow an administrator to choose the type of Archive database to be used. Post-Installation: Now needs to starts with the post installation steps: Once the installation is completed Congratulations! Screen will be displayed as below: Name for the website used for administration: Installation: Setup wizard will guide you through the installation steps and the administrator has to decide/select which directory service to be selected between Active Directory and GFI directory (An AD replacement). GFI Archiver can be installed directly on mail server but not recommended for production environment.

Please let me know if you have any further questions.2. I recommend to upgarde to the latest version of ME2014 - however this will not solve your initial issue with the Public Folders, as the Bug lies not in MailEssentials. I noticed, that you are on the previous verion of MailEssentials 2012.

This is the reason why we released a new feature called 'SpamTag' in the latest version of MailEssentials, - another way to manage spam emails, blocklists and whitelists from the client-side: The Public Folders will be disposed in the future, as of Microsoft. Unfortunately there is nothing we can do in this matter from our side. (You would experience this issue even if GFI wouldn´t be installed on the Server.) Our Developers have reported this issue to Microsoft, and they confirmed that this issue is fixed in Exchange 2013 CU3. This is a well known problem, and GFI is not the only Product, which is affected. This is not a Bug in GFI, but in Microsoft Exchange. The captured error was an internal server error:

Gfi mailessentials for office 365