evolution-list:
> > I just put the string "unique-search-subject1" into
[...]
> Such searches are not done on the server, because all of Subject, To
> and CC headers are cached in the local cache. The server-side search is
> done only/mainly for the body/message contains search type.
Ok, so wha
evolution-list:
> On Mon, 2019-03-04 at 17:21 +0100, fkater--- via evolution-list wrote:
> > How would we debug server side searches...?
>
> this might help:
> https://wiki.gnome.org/Apps/Evolution/Debugging#IMAP
Wow, I'll investigate that.
> I've no idea wh
pete:
>
> > Hm, I wish I could avoid caches -- please help explaining the
> > following behaviour, though:
> >
> > - Create a fresh IMAP account, local sync disabled (20.000+ emails
> > on the server, a lot of subfolders)
> > - Use another mail client to move an email into a subdirectory of
>
evolution-list:
> On Mon, 2019-03-04 at 11:14 +0100, fkater--- via evolution-list wrote:
> > Caching seems required for Evolution to make search work, doesn't
> > it?
>
> Hi,
> no, it doesn't. The local cache/summary (basically the folders.db file
> of
How do we live with large IMAP accounts best?
While the slowness when checking for new folders and mail is still
acceptable, searching / huge caches are an issue. What we did so
far, comparing evolution-3.30.5 with Thunderbird:
Concerning search by local cache
Caching seems required for Evoluti
