After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 769011 - "Empty cache file" when using filter
"Empty cache file" when using filter
Status: RESOLVED DUPLICATE of bug 767564
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.20.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 769412 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-07-20 21:29 UTC by pawel
Modified: 2016-08-12 16:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
CAMEL_DEBUG=imapx output with this incident (30.90 KB, text/x-log)
2016-07-20 21:29 UTC, pawel 		Details

Description pawel 2016-07-20 21:29:54 UTC 
Created attachment 331847 [details]
CAMEL_DEBUG=imapx output with this incident

Hello everyone!

I keep getting errors about "empty cache file" in some particular circumstances:

1. More then 1 concurrent account connections (default).
2. "Apply filters to new messages in Inbox on this server" set (default).
3. One very simple filter:

    Name: <anything>
    Recipients contains <anything>
    Action: <anything>

If I change "Recipients" to "Sender" it works fine so it's mostly about having any filter which uses "Recipients" match.
 
It may be related to this BUG https://bugzilla.gnome.org/show_bug.cgi?id=767564 but I believe I have pointed out much simpler actions to reproduce that.

Regards,
Pawel
Comment 1 Milan Crha 2016-08-02 15:18:54 UTC 
Thanks for a bug report. You are right that this can be a variant of bug #767564, because junk filtering is also just a filter. The log you provided doesn't show any message move, which can be one of the reasons.

Do you still have the complete log, please? I'd like to know the latest SELECT command and its response for both imapx:A and imapx:B connections. Maybe the connection B expects to have selected a different folder than the server has.
Comment 2 Milan Crha 2016-08-08 10:10:31 UTC 
*** Bug 769412 has been marked as a duplicate of this bug. ***
Comment 3 Milan Crha 2016-08-12 16:36:48 UTC 
I made a fix for this issue within bug #767564, thus I mark this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 767564 ***