Re: [Evolution] Time Zone curiosities with EWS

[Milan Crha <mcrha redhat com>]

On Tue, 2015-08-11 at 16:40 +0200, kodiak wrote:
> Yepp, that sounds pretty much like the cause. Workaround is then not 
> to use all day events, rather 24h events starting from 0:00?

        Hi,
yes, that sounds like a good workaround. The question is how you'd
like to treat the all-day events. Nobody said that the Outlook Web App
(OWA) cannot have a bug in itself. The thing is that all-day events
are processed differently, both on the evolution-ews side and on the
server side. There is a special flag marking the event as being all-
day. If I recall correctly, the DATE value is also meant "floating"
which means "it's on that day in whichever timezone the user looks on
it". So it truly feels like the OWA issue.

I tried with an Exchange 2013 server, and the OWA is quite confusing.
I created an all-day event in the Evolution, then watched it in OWA
and it spent two days, instead of only one, but clicking the event it
properly said that it's an All Day event for the one particular date.
I changed the duration of the event to exactly one day in the OWA UI
and then saved it in the Evolution. There is no start/end time change
in the saved component, thus maybe it's an odd thing in evolution-ews
properties.

That said, maybe it's not a bug in the OWA, but the OWA is just more
strict with respect of the properties being set to certain values than
the Outlook itself is. I know the Outlook is more forgiving.

> On Di, 2015-08-11 at 15:48 +0200, Andre Klapper wrote:
> > Might be https://bugzilla.gnome.org/show_bug.cgi?id=352801

I'll close the bug as suggested in its comment #16.

        Bye,
        Milan