Set up chasquid SMTP with explicit DNS and TLS
Follow the small-server setup path, choose the accepted domains, and verify host identity and certificate access before moving MX.
Reviewed
chasquid is an SMTP server for individuals and small groups. Its official how-to uses Debian/Ubuntu, Dovecot, and Let’s Encrypt; use matching package instructions rather than assuming it includes its own IMAP store.
Still comparing small-server options? See chasquid in our Linux mail-server comparison.
Prepare the test domain
- Choose a host with permitted TCP port 25, stable public addressing, and configurable reverse DNS.
- Install chasquid using the supported installation path for your system.
- Configure the served domain, mail hostname, and authentication/delivery relationship using the package’s example files.
- Obtain a certificate for the actual hostname and grant only the required service access to its key/certificate files.
Publish A/AAAA and MX only for the approved domain. A broken IPv6 path can harm delivery even when IPv4 works. Match PTR and the SMTP identity and review SPF/DKIM/DMARC according to your full sending design.
Prove transport readiness
Before moving production mail, verify TLS hostname/trust, an intended local recipient, a rejected unknown recipient, and rejected unauthorized relay. Check logs for a controlled message’s handoff to local delivery.
Automate certificate renewal and the documented daemon reload/restart behavior. Do not make private keys world-readable to fix permissions. If the application needs parsed incoming events, add a deliberately designed processing layer; chasquid’s SMTP service is not a provider webhook API.