(Redmine issue: #7041)

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)

Descriptions of common parameters should be in the documentation, so that the updates do not have to be done on so many places. Additional documentation should be present only for script/daemon specific parameters. (Redmine issue: #3387)

This commit brings in considerable amount of work. When working on this issue everything was so tied together, that I have abandoned all attempts to split it into multiple commits. There are following changes and more:

* Implementation of lightweight chroot for containing the application in single directory tree.
* Design changes in scripts and daemons to implement the lightweight chroot.
* Many configuration file changes to make everything work properly.
* Makefile additions, new targets related to running
* Updated development documentation page.

(Redmine issue: #4216)

Moving constants, adding mentat translations for hawat and modification of coresponding code so hawat can use them for on-fly generating of report messages. Small fixes on mentat side. (Redmine issue: #4498)

(Redmine issue: #4307)

It was possible for the reporter to attach files of any size to the report. The MTA then complained for the message being too big and refused to mail it. Now it is possible for each group co configure maximal attachment size limit (defaults to 10MB). Attachment files exceeding this limit will not be added to the report and user will be informed in the email text to download it from the server. (Redmine issue: #4232)

(Redmine issue: #3378)

* Enhanced data model for reporting settings to contain timezone selection for generated reports.
* Changed data model for reporting settings to allow Null values for many of the settings. In this case system default will be used.
* Updated utility class for configuring reporting settings to enable use of new features mentioned above.
* Updated utility class for configuring reporting settings to enable enforcing most of the values by administrator launching the reporting script.
* Implemented new base form radio field that accepts empty option as valid. This enables implementing for example three state choices like True, False, None, which is great for some reporting settings.
* Updated all Hawat views for working with reporting settings to use new features.
* Enhanced reporter template built-in features, mainly for working with timezones.
* Changed default reporter templates to output dates in chosen timezone.
* Translated all new features to czech localization.

The main result of this commit is, that each group can configure in which timezone it wants to have the dates in the report to be displayed.

(Redmine issue: #3378)

(Redmine issue: #3378)

This feature can be usefull for development and testing purposes. (Redmine issue: #3378)

This patch attempts to make installation of Mentat system as simple as possible by improving the default configuration and cron files for each of the Mentat modules. The goal is to have most of the system up and running after the installation with as less configuration changes as possible. There are however some things that can not be configured in advance, for example email addresses for various reporting, so these are all directed to the local root. (Redmine issue: #3387)

All reports generated by mentat-reporter.py are now accessible via unauthenticated URL protected by security token. This feature enables easy sharing of security information even with people without full access to web interface. (Redmine issue: #3734)

* Added support for default admin contact, which can be used for redirecting emails to administrators.
* Added support for test mode, in which case the all emails are force redirected to admin emails instead of original recipients. This feature can be used for development or testing purposes.

The reporter was configured to run every 10 minutes by default. (Redmine issue: #3387)

This commit introduces the Pythonic reimplementation of mentat-reporter-ng module. It is complete from roughly 70 percent, there are many features that stil need to be implemented as well as some necessary polishing.

The most important next implementation steps:
* thresholding and relapse
* email template improvements
* report section legends with translations
* report web interface improvements
* unauthorized access to reports
* unit testing and bulletproofing

(Redmine issue: #3378)

The mentat-informant.py module is a Python replacement for previous mentat-briefer.py module. It is designed to provide periodical statistical overviews via email. The email reports are localized using babel package and can be translated into any language. Additionally, the reporting engine uses Jinja2 templating system for message rendering, so it enables very easy customization. (Redmine issue: #3377)

* the watchdog time interval is now configurable
* improved content of watchdog email alert
* improved module documentation

(Redmine issue: #3383)

Migration, refactoring and code style unification to support latest PyZenKit and Pynspect libraries.

This huge update represents a lot of work on many parts of the system. After major upgrade in PyZenKit and Pynspect libraries it was necessary to bring this project up to date. There were many changes in the code, lot of refactoring and while all this was done, code quality was improved, documentation written and unit tests modified. Many of these changes simply make sure, that the code works with latest versions of both libraries. This commit is supposed to be a single major feature upgrade, after this only smaller commits will follow to polish this huge amount of work.

(Redmine issues: #3374, #1017, #3361, #3387, #3443)

This is the initial project release. It works, however it should still be considered as alpha release and work in progress. Couple of known issues:
* missing configuration validation
* missing documentation
* missing modules
* only partially working unit tests, not enough coverge of unit tests