Evaluate HTTPS support for Thunderbird autoconfig #1

Open
opened 2026-11-18 23:32:07 +01:00 by André Keller · 0 comments
Owner

Goal

Evaluate adding HTTPS to Postoffice's Thunderbird autoconfiguration endpoint while retaining automatic discovery for managed mail domains.

Current behavior

  • Postoffice serves /mail/config-v1.1.xml through a shared HTTP Nginx virtual host matching autoconfig.*.
  • Each domain publishes autoconfig.<domain> as a CNAME to postoffice1.zrh1.peer42.net.
  • Thunderbird can discover the configuration using the email domain without requiring a manually supplied provider hostname.
  • XML responses contain mail server settings, not passwords, but HTTP discovery allows modification in transit.

Options to evaluate

  1. Per-domain HTTPS virtual hosts and certificates: provision an Nginx vhost and certificate for each autoconfig.<domain>, using existing profile_nginx and profile_certificates mechanisms.
  2. Shared HTTPS virtual host with SAN certificate: manage the certificate's SAN set as domains are added or removed. Consider issuance and renewal limits, certificate lifecycle, and Puppet resource ownership.
  3. Retain HTTP: document the security tradeoff and avoid per-domain TLS provisioning complexity.

Requirements and questions

  • Preserve automatic discovery through autoconfig.<domain>; do not require users to configure a shared hostname manually.
  • Determine how the set of managed domains is supplied to Puppet without coupling base modules to Postoffice or introducing fragile dynamic configuration.
  • Consider initial issuance, renewals, DNS validation, removal of domains, and failures for individual names.
  • Check how Thunderbird handles HTTPS-first discovery, HTTP fallback, and relevant client warnings.
  • Reuse existing certificate and Nginx abstractions where practical; avoid unnecessary complexity.
  • Keep changes independent of the initial mail infrastructure migration unless there is a clear reason to do otherwise.

Completion criteria

Document the evaluated approaches and select an implementation (or explicitly retain HTTP). If HTTPS is chosen, implement certificate/vhost management and verify Thunderbird discovery for at least two domains.

## Goal Evaluate adding HTTPS to Postoffice's Thunderbird autoconfiguration endpoint while retaining automatic discovery for managed mail domains. ## Current behavior - Postoffice serves `/mail/config-v1.1.xml` through a shared HTTP Nginx virtual host matching `autoconfig.*`. - Each domain publishes `autoconfig.<domain>` as a CNAME to `postoffice1.zrh1.peer42.net`. - Thunderbird can discover the configuration using the email domain without requiring a manually supplied provider hostname. - XML responses contain mail server settings, not passwords, but HTTP discovery allows modification in transit. ## Options to evaluate 1. **Per-domain HTTPS virtual hosts and certificates:** provision an Nginx vhost and certificate for each `autoconfig.<domain>`, using existing `profile_nginx` and `profile_certificates` mechanisms. 2. **Shared HTTPS virtual host with SAN certificate:** manage the certificate's SAN set as domains are added or removed. Consider issuance and renewal limits, certificate lifecycle, and Puppet resource ownership. 3. **Retain HTTP:** document the security tradeoff and avoid per-domain TLS provisioning complexity. ## Requirements and questions - Preserve automatic discovery through `autoconfig.<domain>`; do not require users to configure a shared hostname manually. - Determine how the set of managed domains is supplied to Puppet without coupling base modules to Postoffice or introducing fragile dynamic configuration. - Consider initial issuance, renewals, DNS validation, removal of domains, and failures for individual names. - Check how Thunderbird handles HTTPS-first discovery, HTTP fallback, and relevant client warnings. - Reuse existing certificate and Nginx abstractions where practical; avoid unnecessary complexity. - Keep changes independent of the initial mail infrastructure migration unless there is a clear reason to do otherwise. ## Completion criteria Document the evaluated approaches and select an implementation (or explicitly retain HTTP). If HTTPS is chosen, implement certificate/vhost management and verify Thunderbird discovery for at least two domains.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
tools/postoffice#1
No description provided.