Mail backend
The mail backend turns Everlock into a self-hosted mail system with SMTP delivery, authenticated submission, and IMAP access. It keeps incoming mail, mailbox access, forwarding rules, and mail-domain
Documentation
The mail backend turns Everlock into a self-hosted mail system with SMTP delivery, authenticated submission, and IMAP access. It keeps incoming mail, mailbox access, forwarding rules, and mail-domain
A collection of ready-to-use `rules.toml` patterns for common setups. Each example shows both the TOML block for `rules.toml` and the equivalent admin CLI command. For the full field reference, see [M
`rules.toml` lives at the root of the mail store and controls how Everlock handles every message that passes through the system — inbound or outbound. Rules are evaluated in ascending `priority` order
This walkthrough shows how to enable Everlock's authenticated SMTP submission listener, create a sender domain, grant a user permission to send as a mailbox in that domain, and send a test message thr
This walkthrough shows how to start Everlock with inbound SMTP enabled, add a simple `rules.toml`, send a hello-world inbound mail, and verify that the message landed in the versioned mail store. Mail