Skip to content

Docker Compose ΒΆ

The image is published to the GitHub Container Registry for linux/amd64 and linux/arm64:

  • latest and 2, 2.0, 2.0.0 ...: releases;
  • master: the current development state.

This docker-compose.yml runs the service for one domain whose IMAP and SMTP are on mail.example.com, without POP3:

# Put a reverse proxy in front that terminates HTTPS for autoconfig.example.com
# and autodiscover.example.com. Every setting is explained in the documentation:
# https://www.freie-netze.org/autodiscover-email-settings/latest/configuration/
services:
  autodiscover:
    image: ghcr.io/freifunkmuc/autodiscover-email-settings:latest
    restart: unless-stopped
    ports:
      - "127.0.0.1:8000:8000"
    environment:
      DOMAIN: example.com
      COMPANY_NAME: Example
      # the mail servers; an empty host leaves that protocol out
      IMAP_HOST: mail.example.com
      IMAP_PORT: "993"
      IMAP_SOCKET: SSL
      POP_HOST: ""
      SMTP_HOST: mail.example.com
      SMTP_PORT: "587"
      SMTP_SOCKET: STARTTLS
      # optional
      # MOBILESYNC_URL: https://sync.example.com/Microsoft-Server-ActiveSync
      # LDAP_HOST: ldap.example.com
      # LDAP_PORT: "636"
      # LDAP_SOCKET: SSL
      # LDAP_BASE: dc=example,dc=com
      # LDAP_USER_FIELD: uid
      # LDAP_USER_BASE: ou=People,dc=example,dc=com
      # LDAP_SEARCH: (objectClass=inetOrgPerson)

Start it with docker compose up -d, then put a reverse proxy in front. The service only listens on port 8000 of the host's loopback interface; it does not terminate HTTPS itself.

The container runs as an unprivileged user (UID 1000) and needs no volumes: all its state is in the environment.

To check what it answers, see Troubleshooting.