[OGo-Users] Time issues with OGo

[Samuli Seppänen]

OGo has been giving me a headache with it's time issues for quite while,
and many things are not clear to me even after hours and hours of
research in mailinglist archives, google and the plone. As always, I'd
love to contribute an article to the plone about these issues once I get
them cleared.

So, a couple of questions:

1) Should I keep Postgresql database in GMT?

2) Does OGo add it's own DST on top of (Linux) system's own DST? So if
automatic DST is activated in both Linux _and_ OGo, will the OGo clock
be off 1 hour half of the year?

3) Is the only safe setting for TimeZoneName still "GMT"? Can it be
changed to "GMT" on a running system without messing everything up?

4) Is the problem shown below happening due to hypothesis I wrote in
question 2 or something else entirely:

So, when I try to synchronize events between Nokia and OGo by using
Funambol + GroupDAV plugin event begin and endtimes are consistently 1
hour off, either less or more than they ought to be:

An event created in Nokia:

Nokia Timezone: GMT+2 (does automatic DST)
Real begintime: 8.00
Real endtime: 8.05
Vcard begintime: 5.00 (-3 hours)
Vcard endtime: 5.05 (-3 hours)
OGo begintime: 9.00 (+4 hours)
OGo endtime: 9.05 (+4 hours)

This looks good, except for the OGo part. Now onto the OGo event:

OGo TimeZone: EET (GMT+2 with DST)
Real begintime: 7.00
Real endtime: 8.00
Vcard begintime: 3.00 (-4 hours)
Vcard endtime: 4.00 (-4 hours)
Nokia begintime: 6.00 (+3 hours)
Nokia endtime: 7.00 (+3 hours)

Now for some reason OGo adds or decreases 4 hours from begin- and
endtimes, instead of 3 as it should. Nokia on the other hand (correctly)
adds or decreases three hours to the vCard as it is now GMT+2 + DST (1
hour). All this seems like if OGo was adding it's 1 hour on top of the
Linux system's time, even though the system has already switched to DST
(GMT+3).

Thanks in advance,

Samuli