[Tickets #12056] Re: New Kronolith appt w/no invitees sync to iOS, result in greyed item in iOS Calendar

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12056
------------------------------------------------------------------------------
  Ticket             | 12056
  Updated By         | simon at simonandkate.net
  Summary            | New Kronolith appt w/no invitees sync to iOS, result in
                     | greyed item in iOS Calendar
  Queue              | Horde Base
  Version            | 5.0.4
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


simon at simonandkate.net (2013-02-26 23:08) wrote:

> I feel like this could benefit from  some more explanation.
>
> If an invite is received on, AND is dealt with completely from the  
> iOS device, this should work fine.  The flow is something like this:
>
> 1. Device receives request.
> 2. Device creates a tentative event locally on the client's calendar.
> 3. User deals with invitation.
> 4. Device sends the EVENTRESPONSE request to the server.
> 5. Server parses the response, adds the new event to the user's  
> calendar and sends the response email to the organizer.
> 6. The server then deletes the original request email from the  
> INBOX, which triggers a SYNC on the INBOX. THIS IS THE IMPORTANT  
> STEP. This is what causes the client to delete the tentative request.
> 7. Device requests SYNC for INBOX and Calendar, which causes new  
> event to be added, and tentative event to be removed, along with the  
> original request email.
>
> If you keep the original request email, the tentative event will  
> NEVER be removed.  This has nothing to do with the ORGANIZER field.  
> The relevant field here is the (optional) MEETING_STATUS field,  
> which we now always send thanks to iOS's broken behavior.

Thank you Michael, very comprehensive responses.

Can I ask a couple of questions to clarify this please?

I am not certain whether what you are describing here what happens in  
Exchange or in Horde. In our Horde environment, I do not see a lot of  
these steps when a meeting invite is processed. Using your scenario of  
dealing with an invite entirely from an iOS ActiveSync'ed device this  
is what I see in H5:

1. Another user in our Horde system creates a meeting in Kronolith,  
with me as attendee;
2. I get an email in my iOS device's Horde inbox with a .ics (two  
actually, but I understand why now, as this is due to Enhancement 9854);
3. There is nothing in my calendar at this point (either on the iOS  
device or in Kronolith);
4. When I accept a meeting is made in iOS, with ORGANIZER and  
ATTENDEES intact;
5. The new meeting is sync'ed from the iOS calendar to Horde, loses  
ORGANIZER information, and appears in Kronolith;
6. Horde pushes the event out to other ActiveSync devices as an  
appointment, not a meeting.

(Still on iOS device) Note also that when the event is added, and  
after, I never see Accept / Decline / Maybe (which I thought was what  
triggers the EVENTRESPONSE that you mention?) for these Kronolith  
events. Work Exchange meetings I do. All I get is Add to Calendar  
initially, and then if I want to remove it I can only delete.

The invitation email is not deleted, I don't see a tentative meeting  
on receipt of an invitation - the sequence you describe sounds like  
how my work Exchange system works with ActiveSync rather than Horde.  
Am I missing the meaning of your explanation, or is my Horde not  
configured properly to provide this far more integrated calendaring  
than what I am seeing?

Simon