Hi! I use eM Client 9.1.2109 (9967b93) with my corporate Kerio Connect 9.4.2 (6498). EWS connection works good, but each communication session causes the message in Kerio Error Log:
EWS request GetUserConfiguration: error occurred; code 108, description: Not implemented - only CategoryList configuration is supported., auth user: [email protected]
Same issue here. Also using latest eM-Client (Windows) and Kerio Connect 9.4.2. (Windows Server 2022).
Is there a fix nearby?
Regards Wilco
If you are gettings errors on the Kerio server, this is something you will need to discuss with Kerio.
The logs you sent don’t show any issues in eM Client.
No, for sure not.
iPhone, iPad, macos works fine as a Exchange Client for Kerio.
Thunderbird works fine as an IMAP Client (including public Email Folders)
but emclient create errors ?
Why not create a configuration to switch off this request if there is no CategoryList on Kerio ?
1 Like
We have many fixes and workarounds for Kerio server errors and issues which will be in the next release.
There is no ETA as yet, but you can keep an eye on the Release History to see when it is available.
Hi
@Gary do you know if this problem is fixed?
We are using the latest Kerio connect server versions and the latest EM clients but all users create these errors in the server logs and in the EM client.
[18/Feb/2023 06:42:07] EwsOperation.cpp: EWS request GetUserConfiguration: error occurred; code 108, description: Not implemented - only CategoryList configuration is supported., auth user: [email protected]
[18/Feb/2023 06:42:07] EwsOperation.cpp: EWS request FindItem: error occurred; code 339, description: Unsupported restriction type., auth user: [email protected]
Comment from GFI:
It appears that there are EWS properties/Methods used by EMclient which are not supported by KConnect, which causes it to generate an incomplete response which in turn makes the email client act unexpectedly.
The behaviour I noticed at EM Client is that the emails sent correctly and also end up in the sent items but a copy of the email remains in the outbox. I cant confirm 100% certain that this error is related to that behaviour but they do appear at the same time.
The account also seems to syncs really slow to EM client, it takes almost a day to download an account.
Kind regards
Since version 10.0.3530.0 I have the same problem with Kerio Connect 10.0.0.5, connected with EWS.
Seems like the problem has resurfaced again.
I know that eM Client inc states that the problem is with Kerio as the Ews is only partly implemented, and I can mostly agree with that statement.
But As you can see in the message above, Kerio states that the problem is with eM Client as they did not implement it properly with Kerio, and I can mostly agree with that statement too.
But I have now about 50 users with a problem, and eM Client is blaming Kerio, and Kerio is blaming eM Client.
So my question is: How can I solve this problem - can you make a fix that makes it work, or do I have to configure it differently?
I need calender and contacts sync and be able to use delegation.
It would be a shame if I have to tell the customer that they have to go back to Outlook to make things work, as they were happy to leave that software.
I already got an answer from my contact at Kerio:
"EWS is a very bad protocol and already discontinued by MS. I am not aware if the implementation is full or not – I can surely ask that.
We did some tests with eM client before (See internal report) however not with EWS but with IMAP and CalDav & CardDav.
Please let me know what you think about CalDav and CardDav."
So, the advice from Kerio: don’t use EWS, but use IMAP with CalDav and CardDav.
I tested it, and the settings are simple:
CalDav: https://mailserver.yourdomain.com/caldav - supply your email addres including domain and password.
CardDav: https://mailserver.yourdomain.com/carddav/users/yourdomain.com/.public
The second yourdomain.com is your email domain ([email protected])
Hope this helps others.
Well to be honest, EWS is quite good protocol, much better than IMAP, only Kerio implementation of EWS is very bad. The reason why MS is discontinuing EWS is completely different (basically to get rid of third parties and limit functionality for external tools). We’ve reported a lot of bugs to Kerio in their EWS implementation, but they have never fixed anything. Their EWS implementation was meant only for Outlook for Mac and it was very limited. Communication with Kerio is generally very complicated. There are server providers that listen and are willing to fix the bugs and there are some that are not.
I communicated your answer to my contact at Kerio.
No problem with that. These are facts. We would be very happy to work closely with Kerio and together resolve all the compatibility issues, but from the moment the (originally Czech) Kerio has been acquired by GFI it seems they are not interested in such things. It seems they just maintain the current version of Kerio Connect and are not interested in new development and fixing things. We’ve seen quite a lot of our customers leaving Kerio to some other platforms lately because of that.
I just opened a ticket with Kerio for these problems.
I keep you informed.
Can I reach you outside this forum for extra information or to get you in contact with Kerio?
Hi! Now I use eM Client with KMS imap+smtp and all KMS functions work well. CalDav/CardDav for KMS Calendars and Address book work well too, but KMS Tasks is not ideal.