Repository navigation
Troubleshooting
Filip Chochół edited this page Jun 11, 2026
·
1 revision
Check:
-
/autodiscover/autodiscover.xmlis reachable publicly, - the request is routed through HTTPS,
- the email domain is listed in
ALLOWED_DOMAINS, - the returned hostnames match your real IMAP and SMTP servers.
Check:
-
/mail/config-v1.1.xmlworks in a browser orcurl, - the
.well-knownalias is also routed if you expect clients to use it, - the query includes
emailaddress=user@example.com.
Check:
- the URL opens in Safari,
- the response downloads as a profile,
- the email address belongs to an allowed domain,
- the user understands that unsigned profiles may show a warning.
Check:
-
TRUST_PROXY_HEADERS=true, -
TRUSTED_PROXY_IPScontains the proxy or bridge CIDR that connects to the container, - your reverse proxy forwards the real client IP header correctly.
Check:
-
ALLOWED_DOMAINSformatting, - whether the tested address really belongs to one of those domains,
-
RETURN_404_FOR_UNKNOWN_DOMAINif you expect a404response.
Review:
ACCESS_LOG_SKIP_PATHSDISABLE_ACCESS_LOG
By default, health and icon paths can be excluded from access logs.