mirror of
https://blitiri.com.ar/repos/chasquid
synced 2025-12-21 15:17:01 +00:00
b6248f3089
When checking if the dkimsign command exists, the default hook doesn't redirect the output to /dev/null, so if the command is present it will emit unwanted output (interpreted as message headers, as expected). This patch adds the missing redirection. Amended-by: Alberto Bertogli <albertito@blitiri.com.ar> Extended commit message.
This directory contains chasquid's configuration.
- chasquid.conf Main config file.
- domains/ Domains' data.
- example.com/
- users User and password database for the domain.
- aliases Aliases for the domain.
...
- certs/ Certificates to use, one dir per pair.
- example.com/
- fullchain.pem Certificate (full chain).
- privkey.pem Private key.
...
Note the certs/ directory matches certbot's structure, so if you use it you
can just symlink to /etc/letsencrypt/live.
You need at least one certificate, or the server will refuse to start.
Ideally there should be a certificate for each DNS name pointing to you.
Make sure the user you use to run chasquid under ("mail" in the example
systemd files) can access the certificates and private keys.
The user databases can be created and edited with the chasquid-util tool.