Documentation

Tag: mail

Everlock 0.14.0

The 0.14.0 release is the result of four test-coverage passes over the whole server, from 82 to 94 percent of its lines, and of the fixes they turned up: IMAP keeps its message numbers straight across

Everlock 0.7.0

The 0.7.0 release tightens who may do what. Access now derives solely from explicit grants, git repositories can hand out a contributor role that opens pull requests without touching branches, and vau

Everlock 0.5.0

The 0.5.0 release makes HTTPS zero-config, turns the mail backend into a well-behaved internet citizen (outbound STARTTLS, inbound SPF/DKIM verification), and removes the last server restarts from eve

Getting started: IMAP access

This walkthrough shows how to enable IMAP access on an Everlock instance that already receives inbound mail via SMTP. By the end you'll be able to connect Thunderbird, Apple Mail, K-9 Mail, or any sta

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

2026-05-27 mail smtp imap backend

Mail rules cookbook

A collection of ready-to-use `rules.toml` patterns for common setups. Each example shows the TOML block for `rules.toml` and the equivalent admin shell command. Start from the [default rules](/docs/ma

2026-05-25 mail rules smtp

Mail rules reference

`rules.toml` lives at the root of the mail store and decides what happens to every message that passes through Everlock — inbound or outbound. Each rule names the messages it selects under `match` and

2026-05-25 mail rules smtp

Getting started: Inbound mail

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