1Distribution files for maddy2------------------------------34**Disclaimer:** Most of the files here are maintained in a "best-effort" way.5That is, they may break or become outdated from time to time. Caveat emptor.67## integration + scripts89These directories provide pre-made configuration snippets suitable for10easy integration with external software.1112Usually, this is what you use when you put `import integration/something` in13your config.1415## systemd unit1617`maddy.service` launches using default config path (/etc/maddy/maddy.conf).18`maddy@.service` launches maddy using custom config path. E.g.19`maddy@foo.service` will use /etc/maddy/foo.conf.2021Additionally, unit files apply strict sandboxing, limiting maddy permissions on22the system to a bare minimum. Subset of these options makes it impossible for23privileged authentication helper binaries to gain required permissions, so you24may have to disable it when using system account-based authentication with25maddy running as a unprivileged user.2627## fail2ban configuration2829Configuration files for use with fail2ban. Assume either `backend = systemd` specified30in system-wide configuration or log file written to /var/log/maddy/maddy.log.3132See https://github.com/foxcpp/maddy/wiki/fail2ban-configuration for details.3334## logrotate configuration3536Meant for logs rotation when logging to file is used.3738## vim ftdetect/ftplugin/syntax files3940Minimal supplement to make configuration files more readable and help you see41typos in directive names.