Re: [Evolution] Time Zone curiosities with EWS

[Milan Crha <mcrha redhat com>]

On Wed, 2015-08-12 at 10:43 +0200, kodiak wrote:
> I just tested the latest git master (data-server,ews,evolution) and
> created a new all day event in evolution. OWA and Outlook show the 
> correct time span of that event (e.g. "00:00 - We 00:00" on an all 
> day event on Tuesday), but the event is not marked as an all day
> event.

        Hi,
right, I missed that detail, though it seemed like the all-day flag is
treated differently by the Exchange server (see my previous email).
After some tests, the Exchange 2013 also means "all day" as "all day".
My fault (incomplete testing of the change). It's fixed in git master
of evolution-ews now.

> I observed that the Exchange is updating the event of evolution
> after few seconds the event was saved.

That's right, because the server can change the event on save, like
adding default alarm or similar automated server-side changes, thus
evolution-ews fetches the event back to see what was actually stored
on the server.

> Evolution creates the event
> w/o a TZ, and Exchange adds one and sends the update back to
> Evolution, which then shows a TZ (fortunately the correct one).

This is not true for me after the patch. Did you restart also
background processes, namely evolution-calendar-factory? Try to run it
on a terminal like:
   $ EWS_DEBUG=2 /usr/libexec/evolution-calendar-factory -w
then run evolution and repeat the steps. You should see a raw
communication between the server and the evolution-ews, where I see
that the timezone is posted to the server (search for
"messages:CreateItem" (quotes for clarity only) in the log). Of
course, what form of the timezone depends on the server version (the
EWS protocol evolved during the 2007, 2010 and 2013 servers), and I'm
testing with the 2013 server.
        Bye,
        Milan