[horde] [ActiveSync][Kronolith][CentOS 7] wrong event start and end
0x90
0x90 at wmailer.net
Mon Mar 21 18:14:31 UTC 2016
Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
> Quoting 0x90 <0x90 at wmailer.net>:
>
>> Zitat von Michael J Rubinsky <mrubinsk at horde.org>:
>>
>>> Quoting 0x90 <0x90 at wmailer.net>:
>>>
>>>> Hi,
>>>>
>>>> I did set up a new installation of Horde on CentOS 7.2 and have
>>>> troubles with activesync/calendar.
>>>> Using Outlook 2013 as a activesync client causes wrong entries in
>>>> kronolith_events (event_start and event_end) when adding a new
>>>> all day event.
>>>> This is problematic, because outlook clients will crash if they
>>>> see an event that they did not create (e.g. shared calendar or
>>>> new instance of activesync client).
>>>> I have a installation with pretty much same configuration on a
>>>> CentOS 6.7, which is working correct.
>>>>
>>>> Here some infos:
>>>>
>>>> # versions:
>>>> horde 5.2.9
>>>> kronolith 4.2.15
>>>> activesync 2.31.6
>>>>
>>>>
>>>> # config/prefs.d/10-myprefs.php
>>>>
>>>> $_prefs['timezone'] = array(
>>>> 'value' => 'Europe/Berlin'
>>>> [...]
>>>>
>>>>
>>>> # kronolith/config/conf.php
>>>>
>>>> $conf['calendar']['params']['utc'] = true;
>>>> $conf['resource']['params']['utc'] = true;
>>>>
>>>>
>>>> # /etc/php.ini
>>>>
>>>> date.timezone = Europe/Berlin
>>>>
>>>>
>>>> # output from horde php shell
>>>>
>>>> every context gives correct time and timezone when executing
>>>> "echo date("H:i:s").date_default_timezone_get();"
>>>>
>>>>
>>>> # activesync log (adding a new event in Outlook 2013 for
>>>> 2016-03-14, whole day)
>>>> [...]
>>>> DEBUG: [1872] I <POOMCAL:StartTime>
>>>> DEBUG: [1872] I 20160313T230000Z
>>>> DEBUG: [1872] I </POOMCAL:StartTime>
>>>> [...]
>>>> DEBUG: [1872] I <POOMCAL:EndTime>
>>>> DEBUG: [1872] I 20160314T230000Z
>>>> DEBUG: [1872] I </POOMCAL:EndTime>
>>>> [...]
>
> Can you provide the Timezone data that activesync is sending? You
> might need to change the logging to Detailed instead of Protocol in
> the ActiveSync config tab.
>
Yes, of course. It is already logged.
<POOMCAL:Timezone>
xP///00AaQB0AHQAZQBsAGUAdQByAG8AcADkAGkAcwBjAGgAZQAgAFoAZQBpAHQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAFAAMAAAAAAAAAAAAAAE0AaQB0AHQAZQBsAGUAdQByAG8AcADkAGkAcwBjAGgAZQAgAFMAbwBtA
G0AZQByAHoAZQBpAHQAAAAAAAAAAAAAAAMAAAAFAAIAAAAAAAAAxP///w==
</POOMCAL:Timezone>
Which says something like "Mitteleuropäische Zeit" (MEZ or CET).
If I enter the following code in horde php shell I get "CET" as an
answer, which should be correct:
$obj = new Horde_Mapi_Timezone();
echo
$obj->getTimezone($obj->getOffsetsFromSyncTZ("xP///00AaQB0AHQAZQBsAGUAdQByAG8AcADkAGkAcwBjAGgAZQAgAFoAZQBpAHQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAFAAMAAAAAAAAAAAAAAE0AaQB0AHQAZQBsAGUAdQByAG8AcADkAGkAcwBjAGgAZQAgAFMAbwBtAG0AZQByAHoAZQBpAHQAAAAAAAAAAAAAAAMAAAAFAAIAAAAAAAAAxP///w=="));
Sorry for the delay, I was on working trip.
>
> --
> mike
> The Horde Project
> http://www.horde.org
> https://www.facebook.com/hordeproject
> https://www.twitter.com/hordeproject
More information about the horde
mailing list