Hi, we’ve been in touch with one of our users, and our developers have looked into this and tested it using our own Axigen test accounts. What they found is that the supported-privilege-set property does not return a correct value, and for CardDAV it isn’t returned at all.
I completely understand that from a user perspective it used to work in previous versions and now it doesn’t. The change is related to backend improvements on our side – part of that work involved updating how we detect read‑only folders, including checking privilege information consistently across all servers, not just a few. I know it can feel counterproductive when a technical improvement results in what looks like a new issue, but to ensure stable and predictable behavior, we do need the server to provide correct privilege information.
To move this forward, we encourage you to share this specific finding with Axigen as well, specifically the missing or incorrect supported-privilege-set response, since they are in the best position to adjust the server behavior on their side.