[Tickets #13802] Re: Kronolith with iCal sends out to many notifications

noreply at bugs.horde.org noreply at bugs.horde.org
Thu Jan 15 15:17:49 UTC 2015


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

Ticket URL: https://bugs.horde.org/ticket/13802
------------------------------------------------------------------------------
  Ticket             | 13802
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Kronolith with iCal sends out to many notifications
  Queue              | Kronolith
  Version            | 4.2.4
  Type               | Bug
  State              | Duplicate
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-01-15 15:17) wrote:


> this is indeed a showstopper. it might be iCal producing this error,  
> however horde should not send so many emails especially if set in  
> user prefs not to send any notifications

Which is why that ticket is open and currently being worked on now.

>>> another question: isn't horde able to handle internal invitations
>>> (users are known to horde!) just internally, without the need to send
>>> emails?
>>
>> Because this is not how the iTip standard for event organization
>> works. We could implement a separate planning infrastructure just for
>> internal users, but noone has come up with an implementation or
>> intent to sponsor such development yet.

For what it's worth, I've thought about going down this road a number  
of times while working on ActiveSync related appointment stuff. It's  
still somewhere on my "do when I have time" list, though sponsoring  
would definitely help speed it along.

> ok, so my understanding of Horde after several months of testing for  
> small companies is: just use the web interface! do not try to use  
> with os clients, it generates unexpected behaviour especially on OSX.

Currently, for certain use cases, maybe. I would also add "Don't use  
buggy clients" to that list as well.





More information about the bugs mailing list