[horde] Recurrent Appointments not reading timezone info correctly?

Thu May 15 13:45:30 UTC 2014

Quoting Simon Wilson <simon at simonandkate.net>:

> Horde 5.1.6, Kronolith 4.1.5
>
> With all the mayhem that I have been having with iOS and exceptions  
> to recurrent appointments, I set up a new series in Kronolith,  
> hoping that would resolve the issues.
>
> We setup TWO appointments in my wife's calendar, both inviting me as  
> an attendee.
>
> First one was a SINGLE non-recurrent event that came through with  
> times fine, displaying both in Katie's calendar all fine, and  
> showing in my Imp ics viewer fine, and accepted and showing in  
> Kronolith fine.
>
> BEGIN:VCALENDAR
> VERSION:2.0
> METHOD:REQUEST
> X-WR-CALNAME:Calendar of Katie Wilson
> PRODID:-//The Horde Project//Horde iCalendar Library//EN
> BEGIN:VEVENT
> DTSTART:20140626T030000Z
> DTEND:20140626T060001Z
> DTSTAMP:20140515T110757Z
> UID:20140515210757.TVHbHmC8ppAtvb-ImrKk_Q1 at mail.simonandkate.net
> CREATED:20140515T110757Z
> LAST-MODIFIED:20140515T110757Z
> SUMMARY:Loz Back from Hols Cleaning
> ORGANIZER;CN=Katie Wilson:mailto:katie at simonandkate.net
> CLASS:PUBLIC
> STATUS:CONFIRMED
> TRANSP:OPAQUE
> ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:simon at simonandkate.net
> ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:katie at simonandkate.net
> BEGIN:VALARM
> ACTION:DISPLAY
> DESCRIPTION:Loz Back from Hols Cleaning
> TRIGGER;VALUE=DURATION:-PT15M
> END:VALARM
> END:VEVENT
> END:VCALENDAR
>
> We then set up a recurrent appointment from Katie, fortnightly  
> recurrence. That one came through to me displaying as ONE HOUR  
> EARLIER than it was created to be. We are both in the same timezone,  
> and both have Australia/Brisbane set as the default timezone in  
> Horde preferences, but this was not selected when creating the  
> appointment, it was left at 'default'.
>
> The event is in SQL as: 2014-07-08 03:00:00 to 2014-07-08 06:00:00,  
> which is UTC for the correct times (1pm to 4pm), so Kronolith has  
> written the event correctly to SQL for Katie (and it continues to  
> display correctly for her), but the .ics sent to me is either wrong,  
> or being read wrongly by my Imp ics viewer (shows it as Start:  
> Tuesday, July 08, 2014 12:00 pm End: Tuesday, July 08, 2014 3:00 pm  
> Summary: Loz Cleaning, instead of 1pm to 4pm) and is then written  
> into Kronolith wrongly for me.
>
> PHP date time info:
>
> date/time support  enabled
> "Olson" Timezone Database Version  0.system
> Timezone Database  internal
> Default timezone  Australia/Brisbane
>
> Running 'date' on the server gives me the correct time.
>
> Note that we don't have DST in Brisbane at all.
>
> Horde tz config:  ftp://ftp.iana.org/tz/tzdata-latest.tar.gz
>
> The relevant info in that file for Australia/Brisbane is:
>
> # Rule	NAME	FROM	TO	TYPE	IN	ON	AT	SAVE	LETTER/S
> Rule	AQ	1971	only	-	Oct	lastSun	2:00s	1:00	-
> Rule	AQ	1972	only	-	Feb	lastSun	2:00s	0	-
> Rule	AQ	1989	1991	-	Oct	lastSun	2:00s	1:00	-
> Rule	AQ	1990	1992	-	Mar	Sun>=1	2:00s	0	-
> Rule	Holiday	1992	1993	-	Oct	lastSun	2:00s	1:00	-
> Rule	Holiday	1993	1994	-	Mar	Sun>=1	2:00s	0	-
> Zone Australia/Brisbane	10:12:08 -	LMT	1895
> 			10:00	Aus	EST	1971
> 			10:00	AQ	EST
> Zone Australia/Lindeman  9:55:56 -	LMT	1895
> 			10:00	Aus	EST	1971
> 			10:00	AQ	EST	1992 Jul
> 			10:00	Holiday	EST
>
> That looks fine (assuming that is what is actually being used).  
> Nothing in there that should be read as DST.
>
> Any ideas why the recurrent appointments are incorrect times? (see  
> incorrect ics below)
>
> Simon
>
>
> BEGIN:VCALENDAR
> VERSION:2.0
> METHOD:REQUEST
> X-WR-CALNAME:Calendar of Katie Wilson
> PRODID:-//The Horde Project//Horde iCalendar Library//EN
> BEGIN:VEVENT
> DTSTART;TZID=Australia/Brisbane:20140722T120000
> DTEND;TZID=Australia/Brisbane:20140722T130001
> DTSTAMP:20140515T120100Z
> UID:20140515220100.xuUMtVPltSR3XGBGlG7VsA1 at mail.simonandkate.net
> CREATED:20140515T120100Z
> LAST-MODIFIED:20140515T120100Z
> SUMMARY:test
> ORGANIZER;CN=Katie Wilson:mailto:katie at simonandkate.net
> CLASS:PUBLIC
> STATUS:CONFIRMED
> TRANSP:OPAQUE
> ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:simon at simonandkate.net
> ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:katie at simonandkate.net
> RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TU;COUNT=2
> BEGIN:VALARM
> ACTION:DISPLAY
> DESCRIPTION:test
> TRIGGER;VALUE=DURATION:-PT15M
> END:VALARM
> END:VEVENT
> BEGIN:VTIMEZONE
> TZID:Australia/Brisbane
> BEGIN:DAYLIGHT
> TZOFFSETFROM:+1000
> TZOFFSETTO:+1100
> DTSTART:19170101T000100
> TZNAME:EST
> END:DAYLIGHT
> BEGIN:STANDARD
> TZOFFSETFROM:+1100
> TZOFFSETTO:+1000
> DTSTART:19170325T020000
> TZNAME:EST
> END:STANDARD
> BEGIN:DAYLIGHT
> TZOFFSETFROM:+1000
> TZOFFSETTO:+1100
> DTSTART:19420101T020000
> TZNAME:EST
> END:DAYLIGHT
> BEGIN:STANDARD
> TZOFFSETFROM:+1100
> TZOFFSETTO:+1000
> DTSTART:19420329T020000
> TZNAME:EST
> END:STANDARD
> BEGIN:DAYLIGHT
> TZOFFSETFROM:+1000
> TZOFFSETTO:+1100
> DTSTART:19420927T020000
> TZNAME:EST
> END:DAYLIGHT
> BEGIN:STANDARD
> TZOFFSETFROM:+1100
> TZOFFSETTO:+1000
> DTSTART:19430328T020000
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3;UNTIL=19440325T16000Z
> TZNAME:EST
> END:STANDARD
> BEGIN:DAYLIGHT
> TZOFFSETFROM:+1000
> TZOFFSETTO:+1100
> DTSTART:19431003T020000
> TZNAME:EST
> END:DAYLIGHT
> BEGIN:DAYLIGHT
> TZOFFSETFROM:+1000
> TZOFFSETTO:+1100
> DTSTART:19711031T020000
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=19711030T16000Z
> TZNAME:EST
> END:DAYLIGHT
> BEGIN:STANDARD
> TZOFFSETFROM:+1100
> TZOFFSETTO:+1000
> DTSTART:19720227T020000
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=2;UNTIL=19720226T16000Z
> TZNAME:EST
> END:STANDARD
> BEGIN:DAYLIGHT
> TZOFFSETFROM:+1000
> TZOFFSETTO:+1100
> DTSTART:19891029T020000
> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=19911026T16000Z
> TZNAME:EST
> END:DAYLIGHT
> BEGIN:STANDARD
> TZOFFSETFROM:+1100
> TZOFFSETTO:+1000
> DTSTART:19900304T020000
> RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=1SU;UNTIL=19920229T16000Z
> TZNAME:EST
> END:STANDARD
> END:VTIMEZONE
> END:VCALENDAR

Are you sure this is the correct ics,did you misspeak the date, or did  
the ics get the actual date wrong for the first occurrence as well?  
You said it was saved as 2014-07-08 03:00:00, but the DTSTART property  
shows the recurrence starts on 2014-07-22 (which, by chance would be  
the next recurrence date).

-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5869 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/horde/attachments/20140515/69909d9b/attachment-0001.bin>