Note: If any module fails to write data into a queue three times, it will be put in the recovery queue which will be automatically re-processed after a restart of the GFI MailEssentials Backend service. Message Queuing is implemented as a Windows service ( Service name: MSMQ) which needs to be always running for the various reports and notifications to be generated.Įvery email processed by MailEssentials is sent to the messaging queue then processed by GFI MailEssentials Backend service, which writes the corresponding report entry to the reporting database. MailEssentials Reporting module leverages Microsoft Message Queuing (MSMQ) technology which enables MailEssentials to cache data that needs to be written asynchronously to the reporting database. We will look at the following components that affect the correct operation of the Reporting module:ĭescription Microsoft Message Queues (MSMQ) The next section looks at some of the common issues with the reporting framework and how to troubleshoot and resolve issues when they are encountered. Introductionįirebird and Microsoft SQL Server are the supported database management systems that can be configured as the backend for MailEssentials reporting data. If for any reason users are unable to generate reports and spam digests, this article provides some troubleshooting guidelines on possible reasons and resolutions.

In all cases, the Reporting tool will allow reports to be generated on the data that has already been gathered, even when the above conditions are encountered. MailEssentials will, however, stop logging new email data in the reporting database when the Evaluation expires, User limit reached, or if the Subscription becomes inactive. Reports can always be generated when any part of the product is licensed. Reporting functionality is included with all the MailEssentials product editions and is not a separately licensed feature.

GFI Mailessentials User Report