Calendar BUG since version 10.4.4756.0

[stuclark]

I’ve been using eMClient for quite a few years now, mostly without issue; but over the last week I have run into a SERIOUS bug which needs to be actioned by developers.

Since version 10.4.4756.0, there has been a BUG in the calendar functionality of eMClient whereby it returns the “Folder is read only” error when trying to create a calendar event in ANY account configured within eMClient when that account is hosted on an Axigen Mail Server server.

Version 10.4.4209 works CORRECTLY, and there have been no changes in the Axigen server.

I have performed a CLEAN INSTALL of every version of eMClient from the latest (at time of writing 10.4.4867) backwards, and the functionality is BROKEN until I get back to 10.4.4209.

There’s clearly been some change from 10.4.4209 to 10.4.4756 and onwards which has BROKEN this functionality!

[Kim_Fisher]

Hi, I will refer you to this thread:

Server says iCal folder is read only after version 10 update Axigen CalDAV server

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 rea…

[stuclark]

Thanks for the reply confirming the code change which has highlighted this issue.

Could I be provided with more technical detail relating to the errors / missing information being reported by Axigen server? Without this information, there is little point in me raising a ticket with them as I will be unable to explain fully the issues encountered.

[Kim_Fisher]

From the keyboard of our developer:

The Axalis sever incorrectly returns the privilege list in supported-privilege-set as a flat list with no hierarchy despite using the standard DAV privileges specified in RFC 3744. Instead it should be returning the proper privilege hierarchy as shown in RFC 3744 - Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol. Since the hierarchy is missing we miss the information that all privilege includes other privileges, and so on.