Issue Description Following the migration guide , I imported the FileNodes via WebDAV. This leads to the root folder (which stalwart names based on the account’s display name) being imported as a FileNode. For user accounts this regularly contains characters that have to be URL-encoded, such as spac…

Root cause confirmed in the source. DavResources builds hrefs with only the account name component percent‑encoded, not the per‑resource path segments: base_path (e.g. admin@example.com) is escaped with percent_encoding::utf8_percent_encode(..., RFC_3986) when the cache is built (crates/groupware/…

I believe that these are separate issues. While this issue was surfaced due to vandelay automatically creating a directory including a space, stalwart should URL-encode paths that were created via JMAP when exposing via WebDAV. Otherwise it remains possible to create paths via JMAP FileNode that are…

WebDAV hrefs not URL-encoded when 'exported' via vandelay

Issues

Laurendus August 24, 2026, 12:12am 5

Topic		Replies	Views
WebDAV PROPFIND <D:href> is not percent-encoded for FileNode objects created via JMAP, breaking WebDAV clients (spec violation of RFC 3986) Issues	11	156	August 29, 2026
Vandelay migration error due to missing blob links after Stalwart upgrade Issues	9	201	June 30, 2026
Vandelay migration from stalwart v0.15.5 Issues	1	42	August 22, 2026
WebDAV allprop returns DAV:current-user-principal, so Windows Explorer names every file after the account Issues	2	36	October 15, 2026
Stalwart v0.16 prefix for WebUI Questions	5	235	June 10, 2026

WebDAV hrefs not URL-encoded when 'exported' via vandelay

Related topics