Re: [Evolution] [ews] EWS throttling

2017-06-22 Thread Martin Kelly
On Thu, 2017-06-22 at 11:40 +0200, Milan Crha wrote: > Hi, > > On Thu, 2017-06-22 at 10:02 +0100, Pete Biggs wrote: > > I would be disappointed if Evolution were to embrace that > > particular > > Outlook feature! > > I agree. > > > Can you give some form of feedback saying something like

Re: [Evolution] [ews] EWS throttling

2017-06-22 Thread Milan Crha
Hi, On Thu, 2017-06-22 at 10:02 +0100, Pete Biggs wrote: > I would be disappointed if Evolution were to embrace that particular > Outlook feature! I agree. > Can you give some form of feedback saying something like "Download > Paused by Server" and some form of indication how long left t

Re: [Evolution] [ews] EWS throttling

2017-06-22 Thread Pete Biggs
On Thu, 2017-06-22 at 09:58 +0200, Milan Crha wrote: > On Wed, 2017-06-21 at 19:25 +, Martin Kelly wrote: > > 149545 > > Hi, > thanks. I'm wondering what evolution-ews should do in such cases. > Getting this information to UI would not be the best thing, but seeing > that the server says

Re: [Evolution] [ews] EWS throttling

2017-06-22 Thread Milan Crha
On Wed, 2017-06-21 at 19:25 +, Martin Kelly wrote: > 149545 Hi, thanks. I'm wondering what evolution-ews should do in such cases. Getting this information to UI would not be the best thing, but seeing that the server says to wait for almost two and a half minute it would be pretty conf

Re: [Evolution] AppImage version?

2017-06-22 Thread Milan Crha
On Wed, 2017-06-21 at 09:20 -0400, David Burleigh wrote: > Just looking for a stable configuration that is known to do a clean > build of Evolution 3.24. Hi, just a note that evolution requires evolution-data-server of the same version (that's one of the issues, because other (also system)

Re: [Evolution] EWS calendar often out of sync

2017-06-22 Thread Milan Crha
On Wed, 2017-06-21 at 14:02 +0200, Michael Hirmke wrote: > Anything I can do against it? Hi, I can recall only one issue with Exchange 2016 servers, it's https://bugzilla.gnome.org/show_bug.cgi?id=771370 but that's pretty old and you have that fix in your evolution-ews for sure. It would