[Tickets #14840] Re: CalDAV: Need to stop iCAL sending out notifications on any changes on events

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14840
------------------------------------------------------------------------------
  Ticket             | 14840
  Updated By         | randy.meyer at thirdrailgroup.ca
  Summary            | CalDAV: Need to stop iCAL sending out notifications on
                     | any changes on events
  Queue              | Kronolith
  Version            | 4.2.24
  Type               | Enhancement
  State              | New
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


randy.meyer at thirdrailgroup.ca (2020-09-22 14:56) wrote:

Jacques,

Thanks for the reply. This is really a headache. I have been doing a  
bunch of research on the problem. Here's what I have found and the  
situation in more detail.

I have a calendar with a bunch of old and current events that I want  
to copy from a personal calendar (A) to a calendar I am also using for  
my business (B). I have another calendar that I use at my employer?s.

Calendar A - uses ActiveSync
Calendar B - uses Caldav
Calendar C - uses Exchange

When I copy an event from C to A or A to C, no problem. Everything works.
However, when I copy from A to B or C to B, invitations erroneously  
get sent out to everyone on the event.

This caused a huge headache and was a little embarrassing because I  
did not realize that this was happening until a couple people called  
me about why I was resending old invitations.

I merely want to diarize these events in different calendars not  
resend invitations.

What is not clear is whether it is the client that is causing it or  
not. I use EmClient for my email client. When I just do a normal  
update it asks me if I want to send an update notification to the  
other participants. Even though I select no, about 5 minutes later a  
notification gets sent out.

So is that the client not telling the server to not send a  
notification or the server somehow deciding to? Why such a long delay?

Maybe you have the missing piece to this puzzle. Sorry for the long message.