v1.1.0 is out AGPL-3.0, no paid edition

All your mail accounts in one webmail, on your own server.

Plimail brings every IMAP account into one inbox, with calendars, contacts and OpenPGP encryption that works without setup. It runs as a single Docker image behind the proxy you already have.

A mock-up with made-up messages. Pick one to see what Plimail does with it.

Signed lease for the Lisbon office
Ana Ribeiroana@example.org, to sam@example.com

Hi Sam,

The landlord signed this morning. The lease is attached, with the inventory of the furniture. Keys on the 1st.

Ana

Encryption without setup. Plimail creates an OpenPGP key for each of your addresses and unlocks it with your sign-in password. When every recipient has a key, Send becomes Send encrypted. Messages are decrypted in the browser, never on the server.

Everything a mail client needs, nothing to babysit

Plimail keeps your mail on your mail server. It stores headers and the bodies you open in its own database, so lists and search stay fast.

One inbox for every account

  • Any IMAP and SMTP account, with OAuth for Google and Microsoft
  • Server settings found from the address: IMAP, SMTP and CalDAV
  • Threads, search, snooze, rules, categories, scheduled and undo send
  • Folder import and export as .mbox or .eml, keeping dates and flags

Encryption without setup

  • OpenPGP keys created for you and unlocked by your sign-in password
  • PGP/MIME, and keys collected from received Autocrypt headers
  • Encrypted drafts and encrypted Send later
  • Key backup and restore, readable by GnuPG
  • Password-protected messages for people without PGP

Calendars and contacts

  • CalDAV calendars, added from the same address as your mail
  • Send invitations, and answer Yes, Maybe or No
  • Search events by title, place, description or attendee
  • Contacts served over CardDAV, with groups that expand in the composer

Rules that run on the server

  • Sieve filters edited in Plimail and run by your mail server, even when Plimail is closed
  • Out-of-office reply with optional start and end dates
  • Read receipts: ask for one, and answer only when you choose
  • Signature images uploaded once and sent inline

An app on your desktop

  • Installs from Chrome or Edge and opens mailto: links
  • Recently opened mail stays readable offline
  • Fewer, bigger buttons, web push and keyboard shortcuts
  • 11 interface languages, light and dark themes
  • Optional AI with your own key: translate, scam check, proofreading

Sign-in and security

  • Passkeys, TOTP, single sign-on (OIDC) and invite-only registration
  • Change your password and your keys are re-encrypted in the same step
  • Sign-in limits per account and address, STARTTLS required off port 993
  • Message HTML sanitized before it is stored, remote images proxied

Install in three steps

You need Docker with the compose plugin. The compose file starts Plimail, PostgreSQL and Redis.

  1. Download the compose file and the settings

    curl -O https://raw.githubusercontent.com/laupernoe/plimail/main/docker-compose.yml
    curl -o .env https://raw.githubusercontent.com/laupernoe/plimail/main/.env.example
  2. Fill in .env

    Set APP_URL to the address people will open, and generate the secrets.

    # SESSION_SECRET and ENCRYPTION_KEY
    openssl rand -hex 32
    # DB_PASSWORD
    openssl rand -hex 16
  3. Start it

    docker compose up -d

    Open http://your-host:3000 and create the first account; it becomes the administrator. To update, run docker compose pull && docker compose up -d.

docker-compose.yml the whole file, as in the repository
services:
  plimail:
    image: ghcr.io/laupernoe/plimail:latest
    build: .
    restart: unless-stopped
    # Room for a send in flight to finish on a restart (the app waits up to 25 s).
    stop_grace_period: 30s
    env_file: .env
    ports:
      - "${HTTP_PORT:-3000}:3000"
      - "${HTTPS_PORT:-3443}:3443"
    volumes:
      - image_cache:/var/cache/mailflow/images
      # The self-signed certificate, generated at the first start. To serve your own, bind-mount a
      # directory holding cert.pem and key.pem here instead.
      - certs:/certs
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_healthy

  postgres:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: ${DB_NAME:-mailflow}
      POSTGRES_USER: ${DB_USER:-mailflow}
      POSTGRES_PASSWORD: ${DB_PASSWORD:?set DB_PASSWORD in .env}
    volumes:
      - postgres_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U \"$$POSTGRES_USER\" -d \"$$POSTGRES_DB\""]
      interval: 10s
      timeout: 5s
      retries: 5
      start_period: 20s

  redis:
    image: redis:7-alpine
    restart: unless-stopped
    command: redis-server --save 60 1 --loglevel warning
    volumes:
      - redis_data:/data
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 10s
      timeout: 3s
      retries: 5
      start_period: 10s

# The volume names are the ones earlier versions used, so an existing install keeps its data.
volumes:
  postgres_data:
  redis_data:
  image_cache:
  certs:

One image, your proxy

The app serves its own interface. A trusted certificate is the job of the proxy or tunnel you already run.

  • HTTP on 3000 for Caddy, Traefik, nginx or a Cloudflare Tunnel, with WebSocket upgrades on /ws.
  • HTTPS on 3443 with a self-signed certificate made at first start, or your own cert.pem and key.pem.
  • amd64 and arm64 images on the GitHub Container Registry. Migrations run at startup.

A lighter fork of MailFlow

Plimail started from MailFlow and keeps its mail engine. It adds encryption, calendars and a desktop app, and drops plugins, integrations and the native apps.