chasquid(1)

πŸ“¦
version 1.18.0 Β· 3 versions
, in ubuntu resolute, ubuntu stonking

✨ 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_dir dir β€” this is where the config lives. default is /etc/chasquid πŸ’–
  • -config_overrides config β€” 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 to stderr, on top of logging to the file. why not both, right ✨
  • -logfile file β€” the file to log to. heads up: this one enables logtime for you πŸ”₯
  • -logtime β€” include the time when writing the log to stderr ⭐
  • -logtosyslog tag β€” log to syslog, with the tag you give it πŸŽ€
  • -v level β€” 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, see chasquid.conf(5) πŸ’–
  • domains/ β€” per-domain configuration
  • domains/example.com/ β€” domain-specific configuration. can be empty, she's low maintenance πŸ¦‹
  • domains/example.com/users β€” the user and password database for this domain
  • domains/example.com/aliases β€” aliases for the domain
  • certs/ β€” certificates to use, one directory per pair
  • certs/mx.example.com/ β€” certificates for this domain
  • certs/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