Hi again,
[...]
>>Note of the comment in the middle of the [1], about:
>> Workaround Exchange 2016 error, which returns invalid iCalendar
>> object (without 'END:VCALENDAR')
>>Maybe they broke it in some other way.
>Wouldn't be the first time 8-((
as it seems, this exactly was the case.
I
On Mon, 2018-01-29 at 16:50 +0100, Michael Hirmke wrote:
> Please don't feel offended by my mails - this was and is not my
> intention.
Hi,
it's okay. I sometimes forget of bugs, thus some reminders of ongoing
investigations are welcome (I do not mean with it that everyone should
just writ
Hi Milan,
[...]
> Hi,
>evolution-ews itself didn't receive many changes, as can be seen here:
>https://git.gnome.org/browse/evolution-ews/tree/NEWS?h=gnome-3-26
>The change in 3.26.3 truly touches the calendar part [1], though it was
>mainly meant to avoid runtime warnings and or crashes in
On Fri, 2018-01-26 at 21:53 +0100, Michael Hirmke wrote:
> since evolution-ews-3.26.3 handling of recurring appointments got
> even worse.
>
> Before, I had problems when modifying a single appointment in a
> series from evolution calendar gui. This lead to a duplicate entry:
> https://bugzilla.gn
Hi Greg,
[...]
thx for your answer.
>I am using 3.26.4, and we do not use Exchange, but office365 rather. We
>also have a corporate WebEx server at my disposal to test. I just created
>recurring meetings on both systems, and edited them several times. Evo
>Calendar correctly updated the meeti
On Fri, Jan 26, 2018 at 2:53 PM, Michael Hirmke
wrote:
> Hi *,
>
> since evolution-ews-3.26.3 handling of recurring appointments got even
> worse.
>
> Before, I had problems when modifying a single appointment in a series
> from evolution calendar gui. This lead to a duplicate entry:
> https://bu
