v1.13.4 — Regional JMAP endpoint support
Fixes connection failures for accounts whose Fastmail session discovery returns region-pinned endpoints (e.g. phl.api.fastmail.com for the API/upload host and phl-www.fastmailusercontent.com for downloads). The bearer-token host allowlist previously accepted only the two bare hostnames, so any account served from a regional endpoint was rejected before it could connect.
What changed
- The allowlist now matches host shapes rather than a fixed pair of names:
api.fastmail.comandwww.fastmailusercontent.com, each with an optional single regional label (dotted on the API host, hyphenated on the user-content host). Thanks to @JonathanGodley (#106). - The patterns are anchored end-to-end and the region label excludes
., so exactly one label may precede the fixed suffix — spoofs likeevil.phl.api.fastmail.comorphl.api.fastmail.com.attacker.comstill reject. HTTPS remains mandatory, andFASTMAIL_ALLOW_UNSAFE_BASE_URL=trueis still the only way to widen the host check (for self-hosted JMAP).
No configuration change is needed — regional endpoints are accepted automatically. Self-hosted setups are unaffected.
This is an unofficial community project, not affiliated with, endorsed by, or supported by Fastmail.
Full Changelog: v1.13.3...v1.13.4