Setup: self-hosted Vaultwarden 1.37.4, Bitwarden Firefox extension 2026.10.0. Username generator → Forwarded email alias → Fastmail, with “Add website prefix” checked.
On sites that use www., alias generation fails with “Fastmail error: Name is reserved.” For example, https://www.lg.com/ triggers it.
From what I can see in the source, prefix() in integration-context.ts keeps the subdomain. So www.lg.com becomes www_lg, which goes to Fastmail as emailPrefix. Fastmail appears to reserve prefixes starting with www and rejects them. The prefix meets Fastmail’s documented character rules, so the main fix belongs on Fastmail’s side.
Still, Bitwarden could fix it for every forwarder by:
- dropping a leading www when it builds the prefix, and/or
- retrying without a prefix when the forwarder rejects one.
Workaround: uncheck “Add website prefix” for these sites.
Has anyone else seen this? I couldn’t find an existing GitHub issue. If nobody has one, I’ll open one on bitwarden/clients.