mirror of
https://blitiri.com.ar/repos/chasquid
synced 2025-12-22 15:27:02 +00:00
4116c046bc
The default hook will use rspamc (the command-line client of rspamd) if it is installed. rspamc will emit one suggested action, and then the hook will interpret it and return accordingly. Because the possible actions returned by rspamc are user-configured, this patch adds a comment to make it clear that the hook will need adjustment if the configuration uses non-default actions. In particular, the greylisting module (which usually handles the "greylist" action) is not run when using rspamc. This can cause unnecessary rejections and is quite misleading. This patch removes the "greylist" action handling; now the default hook will only reject mail once it reaches rspamd's configured threshold for direct rejection. In the future, a more custom integration with rspamd might be added to allow for rspamd-based greylisting, but until then this is a more reasonable default. Thanks to Jonas Seydel (thor77) and Max Mazurov (fox.cpp@disroot.org) for noticing this issue, helping investigate, and discussing the course of action.
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.