chasquid(1)
β¨ NAME β¨
okay so bestie, welcome to the chasquid(1) manual page π β this one's about chasquid, and it's literally an SMTP (email) server. that's the whole vibe. let's get into it π
πΈ SYNOPSIS πΈ
chasquid [options...]
π¦ DESCRIPTION π¦
so chasquid is an SMTP (email) server that's hyperfocused on three things, no cap: simplicity, security, and ease of operation. it's giving "i just want my mail server to work and not be a whole ordeal" energy π
it's written in Go, and it's distributed under the Apache license 2.0. periodt. β¨
π OPTIONS π
-config_dirdir β this is where the config lives. default is/etc/chasquidπ-config_overridesconfig β config values (in text protobuf format) that override whatever's on disk. lowkey you should basically never need this, bestie β it's only for those very specific deployment situations where editing the config file just isn't feasible π-alsologtostderrβ also log tostderr, on top of logging to the file. why not both, right β¨-logfilefile β the file to log to. heads up: this one enableslogtimefor you π₯-logtimeβ include the time when writing the log tostderrβ-logtosyslogtag β log to syslog, with the tag you give it π-vlevel β verbosity level (1= debug) π-versionβ show version and exit. short, sweet, iconic π
π FILES π
okay so the daemon's config is by default in /etc/chasquid/, and you can change that with the -config_dir flag. slay.
inside that directory, the daemon expects this exact structure, no notes:
chasquid.confβ the main config file, seechasquid.conf(5)πdomains/β per-domain configurationdomains/example.com/β domain-specific configuration. can be empty, she's low maintenance π¦domains/example.com/usersβ the user and password database for this domaindomains/example.com/aliasesβ aliases for the domaincerts/β certificates to use, one directory per paircerts/mx.example.com/β certificates for this domaincerts/mx.example.com/fullchain.pemβ the certificate (full chain)certs/mx.example.com/privkey.pemβ the private key π
ngl the certs/ directory layout matches the one from certbot (the client for Let's Encrypt CA), so you can literally just symlink certs/ to /etc/letsencrypt/live. iykyk β¨
β οΈ okay important one: make sure the user you run chasquid under ("mail" in the example config) can actually access the certificates and private keys. fr fr, don't skip this π«Ά
π CONTACT π
main website: <https://blitiri.com.ar/p/chasquid> π
if you've got questions, comments, or patches, please send them to the mailing list at chasquid@googlegroups.com π and to subscribe, just email chasquid+subscribe@googlegroups.com. come hang out bestie π
π SEE ALSO π
and that's the whole page, bestie π this was chasquid(1), dated 2023-10-03, from the chasquid crew. go forth and send some email, you've got this πβ¨πΈ
π¦ where this page comes from
- ubuntu resolute: chasquid 1.16.0-1 Β· Apache-2.0
- ubuntu stonking: chasquid 1.18.0-1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms