[#14772] CalDAV sync resalts in invitations even when SCHEDULE-AGENT=CLIENT selected
Summary CalDAV sync resalts in invitations even when SCHEDULE-AGENT=CLIENT selected
Queue Kronolith
Queue Version 4.2.23
Type Bug
State Unconfirmed
Priority 2. Medium
Owners
Requester aria@bsc.gwu.edu
Created 2018-01-26 (628 days ago)
Due
Updated 2019-09-01 (45 days ago)
Assigned
Resolved
Milestone
Patch No

Comments
aria@bsc.gwu.edu 2018-01-26 21:42:49
Hi,
When I setup an Outlook client to sync their calendar to Horde 
Groupware Webmail Edition (5.2.22) using Outlook CalDAV Synchronizer, 
if the client creates a meeting invitation using Outlook, the meeting 
invitation is sent both via Outlook (desired) and via Kronolith once 
the CalDAV sync is made.

I find multiple similar tickets, either related to new invitations or 
accepting an invitation that generates duplicate invitations from 
Kronolith.

I have enabled "Set SCHEDULE-AGENT=CLIENT" in CalDAV Synchronizer but 
apparently, this does not work with Horde according to 
https://sourceforge.net/p/outlookcaldavsynchronizer/discussion/general/thread/4f98e2e5/

Is there a solution to this problem?  If no, is there a way I can 
completely disable Horde automatic generation of meeting invitations?

Thanks,
Aria

aria@bsc.gwu.edu 2019-08-05 15:44:26
Hi,

Any chance that this a configuration option can be added that will 
just bypass the server generated e-mails so that I don't have to hack 
the code for Kronolith?  This would be easier than addressing the 
problem itself.  If we could just tell Kronolith to never send out 
automated meeting requests, that would be much simpler.

Thanks,
Aria

Michael Rubinsky <mrubinsk@horde.org> 2019-08-07 01:43:37
> Hi,
>
> Any chance that this a configuration option can be added that will 
> just bypass the server generated e-mails so that I don't have to 
> hack the code for Kronolith?  This would be easier than addressing 
> the problem itself.  If we could just tell Kronolith to never send 
> out automated meeting requests, that would be much simpler.
>
> Thanks,
> Aria

This already exists as a user preference on the master branch in Git.

aria@bsc.gwu.edu 2019-08-07 12:13:05
Thank You!

mbozem@bozem.de 2019-09-01 22:11:57
>
> This already exists as a user preference on the master branch in Git.

This commit is dated 24.12.2015. Is there a chance that this commit 
will make it into the 5.2.x version? We need this fix.

Thank you.