The database sanity check scripts now produce better output, log the output aside to log files for later use and are easier to configure. The usage documentation was revised as well. (Redmine issue: #5101)

(Redmine issue: #5101)

(Redmine issue: #3387)

Fix: Fixed the format of datetime values for generated URLs to processing and reporting dashboards from informant reports.

Also added the links to TXT version of the reports. (Redmine issue: #5101)

(Redmine issue: #5101,#1017)

(Redmine issue: #5101)

(Redmine issue: #5101)

(Redmine issue: #5101,#1017)

(Redmine issue: #3387)

(Redmine issue: #5101)

(Redmine issue: #4216)

Included simple benchmark file for measuring performance of statistical calculations for IDEA messages.

Current version is a very simple script with a huge room for improvements. (Redmine issue: #3443,#1017)

System administrator now has an ability to view the numbers of sent report emails and target email addressess in reporting dashboard and informant emails. This new feature can hopefully enable him/her to spot problems with email reportingmore quickly. (Redmine issue: #5101)

The previous description was not exactly correct, I have found some issues after deployment to test server. (Redmine issue: #5101)

Configuration files and documentation regarding regular event reporting now clearly describe the steps necessary to enable sending emails to real world abuse contacts. (Redmine issue: #5101)

(Redmine issue: #3387)

System administrator should have better information when the report gets redirected to different target email address.

(Redmine issue: #3387)

Users were able to save incorrect reporting settings to the database. I have enforced following policies:

* Default reporting settings are presented to the user. This must be done outsite of the normal 'default' WTForms keyword, because these default get applied when the form is submitted and validated, not when it is displayed for the first time to the user.
* The reporting period may not be zero.
* Validation is enforced only in case the overall reporting settings are 'custom'.

(Redmine issue: #4873)

(Redmine issue: #3361)

(Redmine issue: #3387)

(Redmine issue: #4800)

There was a bug in web UI menu library, which picked the wrong context item for advanced user authentication, which resulted in invalid hiding of menu entries. (Redmine issue: #4798)

(Redmine issue: #3387)

(Redmine issue: #4789)

Because message catalogs can be updated with different commands (with makefile during development and with hawat-cli utility when installed from Debian package), the information about source location can result in unnecessary changes. This patch removes these locations to fix this issue, but in the future it would be better to come up with different solution. I have not implemented that right now, because there is another version of mentat-reporter.py behing the horizon, which merges Hawat`s and Mentat`s message catalogs. (Redmine issue: #4789)

(Redmine issue: #4789)

(Redmine issue: #3387)

When Mentat is installed from Debian packages, there is a possibility now to update local reporting translations with prepared 'hawat-cli repintl' command. When installed directly from git repository local makefile should be used instead, otherwise paths to library and template files are not set up correctly. (Redmine issue: #4789)

(Redmine issue: #3361,#3387,#4216)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

The makefile target 'develop' now pre-builds web interface artifacts. There is a new example configuration file for Apache2 that demonstrates the necessary configuration for Git installations. There is a custom WSGI script file for easier web interface installation from Git. (Redmine issue: #4216)

There are additional context item actions hidden behind the caret in item (group, user) detail page. It was not obvious, hopefully the different icon will be better to understand. Alternatively all buttons could be brought to toplevel, I am however reluctant to do that, because the labels are too long. (Redmine issue: #4874)

(Redmine issue: #4216)

Proper term was "time ago". (Redmine issue: #5018)