gpg-lacre

Author	SHA1	Message	Date
Piotr F. Mieszkowski	b627fde510	Move gpg-mailgate.py logic to lacre.mailgate module gpg-mailgate.py script keeps its role, but only needs to call code defined in lacre.mailgate.	8 months ago
Piotr F. Mieszkowski	4c6fdc52ec	Check mandatory config early, add tests Also: extend failover logging configuration with file-based handler to make sure that the user gets _some_ logs even if they do not configure Lacre at all.	8 months ago
Piotr F. Mieszkowski	75ccfb0850	Use logging module - Replace custom logging code with calls to logging module. - Use logging.config to provide configuration parameters. To make Lacre's logging more flexible, use fileConfig from logging.config to set up all parameters. If the configuration file is missing, use dictConfig with hardcoded reasonable defaults.	9 months ago
Piotr F. Mieszkowski	d90b50f7e7	Extract config, separate logging, split into smaller functions - Move configuration-processing code to a separate module (lacre.config) and provide a simple API to access configuration parameters. - Prepare to use builtin logging module to log diagnostic data. - Rework the configuration-processing file to make it cleaner. - Log additional information while processing configuration. - Reorder functions.	9 months ago