tempmail-vkrm

Managed VKRM edge mail node launcher.

What it does

• Enrolls an admin workspace edge server against the central controller.
• Runs the Rust edge API/runtime in Docker.
• Runs a Postfix sidecar in Docker for local SMTP/mail intake.
• Runs a Caddy sidecar in Docker for the edge API host with HTTP fallback and automatic TLS.
• Splits the edge host so the same domain can serve:
  • the node-local public tempmail API
  • the controller-backed edge management panel
• Syncs active mail domains from the edge runtime into Postfix transport maps.
• Stores message payloads and attachments locally on the edge node.

Commands

tempmail-vkrm
tempmail-vkrm run
tempmail-vkrm status

tempmail-vkrm interactive setup asks for:

• controller URL
• admin email or username
• admin password
• server name
• public IP
• edge API port
• SMTP port
• Postfix hostname

It saves runtime config to:

~/.tempmail-vkrm/config.json

Runtime

The launcher starts:

• tempmail-vkrm-edge
• tempmail-vkrm-postfix
• tempmail-vkrm-proxy

on the Docker network:

tempmail-vkrm-net

Proxy defaults

The edge proxy listens on host ports 80 and 443 by default and uses the API host configured in the workspace panel.

You can override those during setup on a test box with environment variables:

TEMPMAIL_PROXY_HTTP_PORT=18080 \
TEMPMAIL_PROXY_HTTPS_PORT=18443 \
TEMPMAIL_PROXY_TLS_MODE=internal \
tempmail-vkrm

Supported TLS modes:

• auto: normal public certificate flow
• internal: local self-signed Caddy CA for testing
• http: HTTP only