time-shift with recurring appointments

[ljm]

Two separate questions re: recurring appointments being shifted around before/after sync.

Using 4.0.4_GA_456 trial version (12 days left).

First issue.

A recurring appointment created in outlook gets shifted 12 hours when viewed via the web client.

To reproduce:
- from outlook: add a recurring appointment - eg 8am 30 Jan
- select send/receive to sync with server
- log on via the web client
- right-click on the appointment
- select "view series", the time has changed to 8pm (12 hour shift).
- but select "view instance", the time is correct (8am)

Second issue.

This feels like it might be related to the issue above.

To reproduce:
- from web client: add a recurring appointment - eg 8am 30 Jan
- sync from phone (i-mate JAS/JAM - WM5)
- from the calendar view in the phone, the appointment has changed to 31 Jan (shifted 24 hours)
- but the properties of that appointment are selected, the day appears correct (8am 30 Jan)
- log on via the web client
- right-click on the appointment
- select "view series", the time has changed to 8pm (12 hour shift)
- but select "view instance", the time is correct (8am)
- from outlook, send/recieve to sync, then both the instance and series are correct (8am 30 Jan).

Searching the bugzilla, I found this:
http://bugzilla.zimbra.com/show_bug.cgi?id=10861

which on the one hand suggests that recurring appointments might be broken but on the other hand that doesn't sound right.

Any suggestions with how to move forward? The customer really does want recurring appointments...

Otherwise, the installation and migration has been pretty smooth.

[sam]

would highly recommend upgrading to 4.0.5 or waiting for 4.5 GA (should be right around the corner). There have been handful of fixes in mobile, web client and zco regarding recurring appointments.

[ljm]

Upgraded both server and outlook connector to 4.0.5 - behaviour hasn't changed.

Just wondering whether there is a workaround for this - eg. is there an earlier version when recurring appointments were known to work?

Also happy to try to help debug - eg. I can see the SetAppointment SOAP message arriving - can I increase server logging verbosity so as to see the body of the message?

[sam]

To confirm, with the upgraded bits you can reproduce the problem by executing the steps in your original message?

Can you specify the timezones in question in your steps to reproduce. IE, what timezone is the outlook client it, the web client in, the device in?

[jonnyRo]

Would it be possible to get a guide in the wiki on reporting time zone bugs? Time zone swaps are now my most common problem, as I have users on two coasts.

I'm not particularly familiar with the methods used to debug these problems. I really want to learn, please point me in the right direction.

[ljm]

Originally Posted by sam

To confirm, with the upgraded bits you can reproduce the problem by executing the steps in your original message?

Confirmed under 4.0.5.

Originally Posted by sam

Can you specify the timezones in question in your steps to reproduce. IE, what timezone is the outlook client it, the web client in, the device in?

The outlook client is in timezone "(GMT+10.00) Canberra, Melbourne, Sydney)". To check, see: Outlook/Tools/Options/Calendar Options/Timezone

The server ought to be in the same timezone. I don't know how to confirm this, but:
- /etc/timezone is set correctly
- /etc/localtime matches the relevant file under /usr/share/zoneinfo/Australia

Is there any way I can query zimbra to ask what timezone it thinks it's in? The reason I ask is this soap exchange.

The <SetAppointmentRequest> sent by outlook looks ok:

<SetAppointmentRequest l="10">
<default ptst="NE">
<m>
<tz id="(GMT+10.00) Canberra, Melbourne, Sydney" stdoff="600" dayoff="660">
<standard week="-1" wkday="1" mon="3" hour="3" min="0" sec="0"/>
<daylight week="-1" wkday="1" mon="10" hour="2" min="0" sec="0"/>
</tz>
<inv method="REQUEST" fb="B" transp="O" allDay="0" name="Fred birthday" loc="" uid="blah">
<s d="20070122T080000" tz="(GMT+10.00) Canberra, Melbourne, Sydney"/>
<e d="20070122T083000" tz="(GMT+10.00) Canberra, Melbourne, Sydney"/>
<or name="My Name" a="blah@example.com"/>
<recur>
<add>
<rule freq="YEA">
<bymonthday modaylist="22"/>
<bymonth molist="1"/>
</rule>
</add>
</recur>
</inv>
<su>Fred birthday</su>
<mp ct="text/plain"> <content> </content> </mp>
</m>
</default>
</SetAppointmentRequest>

The subsequent <SyncResponse> from the server has a reference to Tijuana time which I can't understand and this makes me wonder whether zimbra thinks it's in tijuana? Perhaps I haven't set something that needs to be set on the server? Although even then, there's clearly a bug because (as reported in the first posting) the web client shows the series time shifted and the instance time correctly.

<SyncResponse md="1169428772" token="902">
<appt ms="902" md="1169428772" uid="blah" l="10" id="381">
<inv seq="0" compNum="0" id="380">
<tz dayoff="-420" stdoff="-480" id="(GMT-08.00) Pacific Time (US & Canada) / Tijuana">
<standard sec="0" hour="2" wkday="1" min="0" mon="10" week="-1"/>
<daylight sec="0" hour="2" wkday="1" min="0" mon="4" week="1"/>
</tz>
<tz dayoff="660" stdoff="600" id="(GMT+10.00) Canberra, Melbourne, Sydney">
<standard sec="0" hour="3" wkday="1" min="0" mon="3" week="-1"/>
<daylight sec="0" hour="2" wkday="1" min="0" mon="10" week="-1"/>
</tz>
<replies/>
<comp type="event" seq="0" transp="O" loc="" fb="B" status="CONF" apptId="381" isOrg="1" fba="B" compNum="0" rsvp="0" x_uid="040000008200e00074c5b7101a82e00800000000d0b fffe0c43dc701000000000000000010000000cb7a9566dc2e6 546b25268f34ab9c4f5" name="Fred birthday">
<recur>
<add>
<rule freq="YEA">
<bymonthday modaylist="22"/>
<bymonth molist="1"/>
</rule>
</add>
</recur>
<s d="20070122T080000" tz="(GMT+10.00) Canberra, Melbourne, Sydney"/>
<e d="20070122T083000" tz="(GMT+10.00) Canberra, Melbourne, Sydney"/>
<or url="blah@example.com"/>
</comp>
</inv>
</appt>
</SyncResponse>

[sam]

Yup, something does indeed look fishy.

Do you have the SetAppointmentResponse for the SetAppointmentRequest above (including the soap header)?

[ljm]

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<context xmlns="urn:zimbra">
<sessionId id="3">3</sessionId>
<change token="902"/>
</context>
</soap:Header>
<soap:Body>
<SetAppointmentResponse apptId="381" xmlns="urn:zimbraMail"><default id="380"/></SetAppointmentResponse>
</soap:Body>
</soap:Envelope>

[ljm]

A completely unrelated issue - looking at the soap exchange I noticed that the response to NoOpRequest is:

{Body:{NoOpResponse:{_jsns:"urn:zimbraMail"}},Head er:{context:{sessionId:[{_content:"4",id:"4"}],change:{token:1000},_jsns:"urn:zimbra"}},_jsns:"u rn:zimbraSoap"}

which doesn't look like valid xml to me!

[sam]

Responses can be sent back in JSON or XML. Thats probably the web client requesting the response be returned in JSON format.

From the request/response you posted, its not clear how that other PST timezone snuck its way in. Please file a bug and include the information above.