Wed, 08 Apr 2026 16:56:32 +0000 https://bugs.horde.org/ticket/14772 CalDAV sync resalts in invitations even when SCHEDULE-AGENT=CLIENT selected 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 Fri, 26 Jan 2018 21:42:49 +0000 https://bugs.horde.org/ticket/14772#t92714 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 Mon, 05 Aug 2019 15:44:26 +0000 https://bugs.horde.org/ticket/14772#t93434 > 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. Wed, 07 Aug 2019 01:43:37 +0000 https://bugs.horde.org/ticket/14772#t93435 Thank You! Wed, 07 Aug 2019 12:13:05 +0000 https://bugs.horde.org/ticket/14772#t93439 > > 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. Sun, 01 Sep 2019 22:11:57 +0000 https://bugs.horde.org/ticket/14772#t93454