Peter Bieringer

after changing to use of "mod_authz_unixgroup.so" all works fine.

Until next release is published, I have now created new builds for Fedora and EPEL containing latest upstream + this patch. Fedora is already in testing repository, EPEL is triggered....

I can't replicate the issue - precondition - "new account" user is known in authentication database - but has never logged on so far - therefore no "user" subdirectory exists...

https://github.com/Kozea/Radicale/pull/1455 extended logging related to "mkcol"

"radicale" depends in this case 100% on vobject -> one has to wait until "vobject" got proper fixed

Is this special vcard passing the validator without any errors? Please check with https://icalendar.org/validator.html But even if it's the case, as one see, it's related to `vobject`.

Thank you for tracing down the issue. > I'm also unaware of any past issues this might have had in Radicale: perhaps it's disabled for a reason here? Potentially nobody...

PR merged, please test. Once test case is added, this issue can be closed.

Potential solution would be adding a custom flag into `.Radicale.props` (https://github.com/Kozea/Radicale/wiki/Collection-Storage#file-radicaleprops) which prevents writing to a collection on server side and extending the WebUI to add/remove/change this flag by custom...

should be solved by https://github.com/Kozea/Radicale/pull/1271