May 6 2022
Nov 22 2019
does this issue apply to the enterprise version of Kolab 16 as well? We're currently evaluating Kolab (opensource version) to see if it fits our needs, but incomplete ActiveSync would be somewhat of an issue for us.
Jul 5 2019
Fixed in 91e57e1f7367.
Jul 2 2019
Submitting patch for review blocked due to https://git.kolab.org/T5462
Jul 1 2019
Mar 30 2019
Mar 27 2019
Nobody with a support subscription runs in to this "problem", therefore nobody needs this "feature", and it is therefore closed off as irrelevant.
Mar 22 2019
Correcting the priority from 60/40 to Normal
Oct 15 2018
Jun 11 2018
Feb 13 2018
@machniak is there any update to how streamlining Activesync subscription logic may work?
Dec 28 2017
Wouldn't the simple solution to be allow folders to be created as subfolders of INBOX @machniak
Nov 7 2017
Jul 18 2017
What is more. When user receives iTip response for an exception and updates the event, Outlook will incorrectly send Sync-Add command for the new exception, which then creates a duplicate object. Which leads to a "missing" event in Roundcube and error in syncroton log. This in itself is another issue, but I see that with correct ExceptionStartTime Outlook does not send such requests.
Jul 9 2017
So, I started working on this. I thought it's reasonably simple to implement, but testing this with Outlook 2013 I see a lot of strange comminication that is not described in the documentation. It sends redundant Sync commands with event updates, so in the end, after accepting an invitation the event ends up being still in un-responded state.
Jun 27 2017
no, I didn't
@adomaitis Looks like both DayOfWeek and Until are optional. In this case I think we just should not include DayOfWeek in the response. Did you test that?
Jun 26 2017
Jun 21 2017
Jun 20 2017
SendResponse element was added in version >=16.0 of the ActiveSync protocol, which means it is optional and can be excluded from the initial implementation. Also, from what I see it is about calendar events. I didn't found any information about handling of iTips for TODO (tasks), so they are probably ignored.
One additional change is required in the ldap_public config:
Note: To make the LDAP addressbook sources working we need two additional // fields ('uid' and 'changed') specified in the fieldmap array // of the LDAP configuration ('ldap_public' option). For example: // 'uid' => 'nsuniqueid', // 'changed' => 'modifytimestamp',
Jun 16 2017
This is done. Required configuration for Outlook:
$config['activesync_gal_sync'] = array('windowsoutlook'); $config['activesync_multifolder_blacklist_contact'] = array('windowsoutlook');
Jun 15 2017
Jun 7 2017
Jun 3 2017
While using constant folder identifiers would be good long term solution, in meantime I've found a simpler way. With rS57c38b7aede3 the device will correctly handle folder renames and re-synchronize folder hierarchy and renamed folder content. Closing.
May 26 2017
Fixed in cae366edcab1b.
Activesync supports reminders (alarms) only as "the number of minutes before a calendar item start time". So, we can just ignore these alarms or check if the datetime is before start time of the event and calculate number of minutes.
May 10 2017
Mar 23 2017
You are right. It's not implemented at all.
Mar 6 2017
I also think that revealing activesync_init_subscriptions setting to users may be too complicated and confusing for most of them. So, I'd keep this option as is.
Feb 10 2017
Feb 9 2017
Confirmed. The problem here is that Outlook completely ignores the error we send in response to Sync request (after FolderUpdate). It should re-synchronize folders hierarchy according to the protocol specification.
Outlook and MS ... why I'm not surprised ...
let me know about the commit, I will try on my side.
@adomaitis I'm testing a fix and can't make Outlook display an error. I tried valid ActiveSync response with different error codes and even http error 500. In all cases Outlook just ignores the error and displays the folder as any other folder. So, while I'll commit the change it looks that it's not possible to tell Outlook the operation failed.
Feb 8 2017
Feb 6 2017
Note to myself: See https://msdn.microsoft.com/en-us/library/gg651087(v=exchg.80).aspx for list of possible error status codes. Looks like code 3 might suit the best this case, but there are a few other cases that we might want to distinguish in error code.