{{define "title"}}Server Settings - Email Server{{end}} {{define "extra_css"}} {{end}} {{define "content"}}

Server Settings

Server Configuration
Plain IMAP port (no STARTTLS offered)
Implicit-TLS IMAP port (IMAPS)
RFC 8620/8621 HTTP+JSON mail access — reads/writes the same mailboxes IMAP uses, not a separate store
Dedicated HTTPS port (always TLS, shares the admin/webmail UI's certificate)
Port for plain/IP-whitelisted SMTP connections
Port for direct-TLS authenticated SMTP connections
Plain HTTP port for this admin web interface
Self-signed by default, or the Let's Encrypt cert once enabled
Custom SMTP banner (empty by default)
Database Configuration
Logging Configuration
Email Relay Configuration
Rspamd (Spam Scoring)
Optional; the built-in heuristic spam score always runs regardless of this setting.
Virus Scanning (ClamAV)
Off by default. Scans every inbound message once via an external clamd instance (not installed/managed by this server — point it at one you're already running) before delivery; an infected message is hard-rejected. If the scanner is unreachable, mail still delivers normally rather than being blocked.
Two-Factor Authentication (MFA)
Require every admin account (global or domain-scoped) to set up TOTP/passkey MFA before using the dashboard
Require MFA before a mailbox owner can create new app passwords in the self-service portal — overridable per-domain or per-mailbox
TLS/SSL Configuration
The "custom" certificate: self-signed on first run, or your own uploaded cert/key above.

Which certificate each TLS listener uses — custom (above), or one of the two Let's Encrypt certificates managed on the Let's Encrypt page. Independent per listener, e.g. an HTTP-01 cert for mail while the dashboard keeps a DNS-01 or custom cert.

Changing which certificate a listener uses needs a restart to take effect. Once assigned, that listener's certificate then hot-reloads automatically on every future obtain/renew, no restart needed for that part.
DKIM Configuration
Shared DKIM Key (CNAME delegation)

Lets a domain CNAME its DKIM selector to one server-wide record instead of publishing its own — see the "Shared DKIM Key" card on the DKIM page to generate/regenerate it, and each domain's Edit DKIM page to opt in.

What a domain's one-time CNAME points at. Leave blank to keep this feature unavailable.
days
Blank/0 = manual only (default) — use the Regenerate button on the DKIM page instead.
Attachments Configuration
Make sure the path exists and is writable by the server process
Server restart required after changing settings
{{end}} {{define "extra_js"}} {{end}}