Re: [Evolution] Getting “Failed to issue REPORT: HTTP error code 404 (Not Found)”.

2019-01-07 Thread Milan Crha via evolution-list
On Sat, 2019-01-05 at 22:32 +, Graham Sivill wrote: > I have posted a selected highlights which did get accepted > but if Milan or others need the full version extracts of the commands > I will do as you suggest and send a link to the files in my Google > Drive. Hi, no need for that, t

Re: [Evolution] Getting “Failed to issue REPORT: HTTP error code 404 (Not Found)”.

2019-01-07 Thread Graham Sivill
> From: Milan Crha via evolution-list > Reply-To: Milan Crha > To: evolution-list@gnome.org > Subject: Re: [Evolution] Getting “Failed to issue REPORT: HTTP error > code 404 (Not Found)”. > Date: Mon, 07 Jan 2019 11:54:46 +0100 > > On Sat, 2019-01-05 at 22:32 +, Graham Sivill wrote: > > I h

Re: [Evolution] Accessing Exchange (ews) through a proxy (ssh/socks5)

2019-01-07 Thread Michael Parson
On Sun, 6 Jan 2019, Ángel wrote: Subject: Re: [Evolution] Accessing Exchange (ews) through a proxy (ssh/socks5) I didn't know evolution could work through a socks proxy. I would try accesing ews using a normal ssh port-forwarding for the destination and port you are trying to reach. That is w

Re: [Evolution] search feature slow - in one account only

2019-01-07 Thread Herr Oswald
> To add to that: there is a setting to keep stored for offline only > part > of the folder, like several recent weeks/months/... Which means not > every message can be downloaded locally. > > Having an optimization of "whole folder is stored for offline", then > avoid server-side searching, can b