- Jun 06, 2019
-
-
Jan Zerdik authored
(Redmine issue: #4500)
-
Jan Mach authored
(Redmine issue: #3361)
-
- Jun 05, 2019
-
-
Jan Mach authored
I have merged work done by my coleague to main development branch for testing and deployment.
-
- Jun 04, 2019
-
-
Jan Zerdik authored
-
- Jun 03, 2019
-
- May 24, 2019
-
-
-
Jan Mach authored
Added more readable From: header instead of default root. Added extended email headers X-Mentat-Report-Class and X-Mentat-Report-Type to enable automated report processing. Changed the log directory to default /var/mentat/log. (Redmine issue: #5101)
-
Jan Mach authored
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)
-
- May 23, 2019
-
-
Jan Mach authored
(Redmine issue: #5101)
-
- May 22, 2019
-
-
Jan Mach authored
- May 21, 2019
-
-
Jan Mach authored
The previous description was not exactly correct, I have found some issues after deployment to test server. (Redmine issue: #5101)
-
Jan Mach authored
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)
-
Jan Mach authored
-
Jan Mach authored
System administrator should have better information when the report gets redirected to different target email address.
-
- May 20, 2019
-
-
Jan Mach authored
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)
- May 14, 2019
-
- May 13, 2019
-
- May 10, 2019
-
-
Jan Mach authored
(Redmine issue: #4789)
-
Jan Mach authored
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)
- May 07, 2019
-
-
Jan Mach authored
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)