[Tickets #12912] Re: Event handling through ActiveSync

Discussion:

(too old to reply)

n***@bugs.horde.org

2014-01-15 04:28:25 UTC

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

Ticket URL: http://bugs.horde.org/ticket/12912
------------------------------------------------------------------------------
Ticket | 12912
Updated By | ***@simonandkate.net
Summary | Event handling through ActiveSync
Queue | Horde Framework Packages
Version | FRAMEWORK_5_1
Type | Bug
State | Unconfirmed
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

***@simonandkate.net (2014-01-15 04:28) wrote:

Next piece in the puzzle. I realise this is a few pieces all together,
I am trying to pull together all of the issues that we have with
meeting handling in an iOS / Android / Horde environment.

A new recurrent appointment is created by my wife in iOS, and I am
added as an attendee. This successfully syncs up to Horde, and I
receive an invite.

In Imp this presents as:

Katie Wilson requests your presence at "Loz cleaning - yeah!!!".
Start: Tuesday, January 21, 2014 1:00 pm
End: Tuesday, January 21, 2014 3:59 pm
Summary: Loz cleaning - yeah!!!
Location: EMP
Attendees:
Name Role Status
Wilson Simon Required Participant Awaiting Response
Actions: Accept and add to my calendar GO

There is no indication that this is a recurrent event, yet the ICS
shows that it is a recurrent event (see below). Accepting the
invitation in Imp correctly generates a fortnightly recurrent event in
Kronolith.

Return-Path: <***@simonandkate.net>
Received: from murder ([unix socket])
by server04.simonandkate.lan (Cyrus
v2.3.7-Invoca-RPM-2.3.7-12.el5_7.2) with LMTPA;
Tue, 14 Jan 2014 21:17:42 +1000
X-Sieve: CMU Sieve 2.3
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.simonandkate.net (Postfix) with ESMTP id E72C05768F
for <***@simonandkate.net>; Tue, 14 Jan 2014 21:17:41 +1000 (EST)
X-Virus-Scanned: amavisd-new at simonandkate.net
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=6.2
tests=[ALL_TRUSTED=-1, BAYES_05=-0.5, MIME_QP_LONG_LINE=0.001]
autolearn=ham
Received: from mail.simonandkate.net ([127.0.0.1])
by localhost (mail.simonandkate.net [127.0.0.1]) (amavisd-new, port 10026)
with LMTP id gLfV+bw9Mzku for <***@simonandkate.net>;
Tue, 14 Jan 2014 21:17:41 +1000 (EST)
Received: from emp06.simonandkate.lan (emp06.simonandkate.lan [192.168.1.230])
by mail.simonandkate.net (Postfix) with ESMTP id 05B1457661
for <***@simonandkate.net>; Tue, 14 Jan 2014 21:17:41 +1000 (EST)
Content-Type: multipart/alternative;
boundary=Apple-Mail-8275EB3F-E878-4C3A-BFEE-A2ABF43799E7
Content-Transfer-Encoding: 7bit
Subject: Loz cleaning - yeah!!!
From: ***@simonandkate.net
Message-Id: <1B8DC427-6966-4122-BA01-***@simonandkate.net>
Date: Tue, 14 Jan 2014 21:17:42 +1000
To: Wilson Simon <***@simonandkate.net>
Mime-Version: 1.0 (1.0)

--Apple-Mail-8275EB3F-E878-4C3A-BFEE-A2ABF43799E7
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: 7bit

--Apple-Mail-8275EB3F-E878-4C3A-BFEE-A2ABF43799E7
Content-Type: text/calendar;
charset=utf-8;
name=meeting.ics;
method=REQUEST
Content-Transfer-Encoding: quoted-printable

BEGIN:VCALENDAR=0D=0ACALSCALE:GREGORIAN=0D=0AMETHOD:REQUEST=0D=0APRODID:-//A=
pple=20Inc.//iPhone=203.0//EN=0D=0AVERSION:2.0=0D=0ABEGIN:VTIMEZONE=0D=0ATZI=
D:Australia/Brisbane=0D=0ABEGIN:STANDARD=0D=0ADTSTART:20010101T000000=0D=0AT=
ZNAME:AEST=0D=0ATZOFFSETFROM:+1000=0D=0ATZOFFSETTO:+1000=0D=0AEND:STANDARD=0D=
=0AEND:VTIMEZONE=0D=0ABEGIN:VEVENT=0D=0AATTENDEE;CN=3D"Wilson=20Simon";CUTYP=
E=3DINDIVIDUAL;PARTSTAT=3DNEEDS-ACTION;RSVP=3D=0D=0A=20TRUE:mailto:***@sim=
onandkate.net=0D=0ACREATED:20140114T111739Z=0D=0ADTEND;TZID=3DAustralia/Bris=
bane:20140121T160000=0D=0ADTSTAMP:20140114T111739Z=0D=0ADTSTART;TZID=3DAustr=
alia/Brisbane:20140121T130000=0D=0ALAST-MODIFIED:20140114T111739Z=0D=0ALOCAT=
ION:EMP=0D=0AORGANIZER;CN=3D"Katie=20Wilson";EMAIL=3D"***@simonandkate.net=
":mailto:katie@=0D=0A=20simonandkate.net=0D=0ARRULE:FREQ=3DWEEKLY;INTERVAL=3D=
2=0D=0ASEQUENCE:0=0D=0ASUMMARY:Loz=20cleaning=20-=20yeah!!!=0D=0ATRANSP:TRAN=
SPARENT=0D=0AUID:DA40D0E593674F56B4120EA1A06A4F1F0=0D=0AX-MICROSOFT-CDO-INTE=
NDEDSTATUS:FREE=0D=0AEND:VEVENT=0D=0AEND:VCALENDAR=0D=0A=

--Apple-Mail-8275EB3F-E878-4C3A-BFEE-A2ABF43799E7--

On my Android devices, the event invitation comes through OK, with an
attached ICS showing as a fortnightly recurrent
RRULE:FREQ=WEEKLY;INTERVAL=2 yet the UI does not show it as recurrent.

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-15 15:54:25 UTC

Permalink

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-15 16:03:19 UTC

Permalink

Post by n***@bugs.horde.org
There is no indication that this is a recurrent event, yet the ICS
shows that it is a recurrent event (see below). Accepting the
invitation in Imp correctly generates a fortnightly recurrent event
in Kronolith.

If the iTip is correct, and imports correctly into Kronolith, and
displays correctly in other clients, then the issue is in IMP"s iTip
viewer, not ActiveSync or Kronolith.

Please create an IMP enhancement ticket to add this to the iTip viewer.

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-15 16:10:14 UTC

Permalink

How does an event deletion on iOS that submits a single deletion
request end up as two event emails in Imp, neither of which bear
accurate connection to what actually happened (deletion of the
entire series)?

Because, according to the log you provided, the iOS client is not
deleting the event, it's modifying it, and only deleting a single
exception to that event, not the event itself.

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-15 16:18:42 UTC

Permalink

2014-01-14T21:14:36+10:00 DEBUG: [6013] I <Modify>

^^^ This is an event *modification*, not *deletion*. ^^^

<snip unimportant values>

2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:MeetingStatus>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 1
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:MeetingStatus>

^^^ A value of (1) here indicates that this is a "meeting", as opposed
to a value of (5) which would indicate that this is a cancelled
meeting. ^^^

2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Recurrence>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Type>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 1
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Type>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Interval>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 2
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Interval>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:DayOfWeek>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 4
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:DayOfWeek>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Until>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 20131231T030000Z
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Until>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:FirstDayOfWeek>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 0
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:FirstDayOfWeek>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Recurrence>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Exceptions>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Exception>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Deleted>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 1
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Deleted>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I
<POOMCAL:ExceptionStartTime>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 20131217T030000Z
2014-01-14T21:14:36+10:00 DEBUG: [6013] I
</POOMCAL:ExceptionStartTime>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Exception>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Exception>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I <POOMCAL:Deleted>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 1
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Deleted>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I
<POOMCAL:ExceptionStartTime>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I 20131203T030000Z
2014-01-14T21:14:36+10:00 DEBUG: [6013] I
</POOMCAL:ExceptionStartTime>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Exception>
2014-01-14T21:14:36+10:00 DEBUG: [6013] I </POOMCAL:Exceptions>

^^^ This is the section that defines the recurrence and any
exceptions. As you can see, it indicates that the exceptions are being
deleted. ^^^

So, from this log snippet, the only thing that is happening server
side is that a number of the exceptions to the recurring event are
deleted - meaning the original occurrences are now "back on" so to
speak.

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-15 16:21:07 UTC

Permalink

There seems to be very little relationship between the action that
was taken and what gets communicated through Horde.

This is not true. Horde is doing *exactly* what the iOS client is
asking. The only thing I would agree with here is that when an
exception is deleted, it might be confusing to receive the two iTIps -
one for the exception being deleted and one for the original event
being modified (because the previous exceptions are no longer valid,
and the original event series is now active).

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-16 09:17:25 UTC

Permalink

Post by n***@bugs.horde.org
In the future, please use attachments to provide the log file data.

Yep, sorry about that...

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-16 09:31:13 UTC

Permalink

Post by n***@bugs.horde.org

If the iTip is correct, and imports correctly into Kronolith, and
displays correctly in other clients, then the issue is in IMP"s iTip
viewer, not ActiveSync or Kronolith.
Please create an IMP enhancement ticket to add this to the iTip viewer.

For posterity, recorded here: http://bugs.horde.org/ticket/12919

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org

n***@bugs.horde.org

2014-01-16 11:06:57 UTC

Permalink

Post by n***@bugs.horde.org

There seems to be very little relationship between the action that
was taken and what gets communicated through Horde.

This is not true. Horde is doing *exactly* what the iOS client is
asking. The only thing I would agree with here is that when an
exception is deleted, it might be confusing to receive the two iTIps
- one for the exception being deleted and one for the original event
being modified (because the previous exceptions are no longer valid,
and the original event series is now active).

OK, it appears to send an invitation as opposed to a cancellation when
events AFTER the original one is opened, as Apple prompts to "Delete
this event" or "delete all future events".

So it leaves events prior to the one opened as the delete 'master'.

I'm going to have a play with sequences and events over the next week
or so, will post back with results.

--
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: bugs-***@lists.horde.org