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 754935 - Error while Filtering new messages in 'INBOX'.
Error while Filtering new messages in 'INBOX'.
Status: RESOLVED DUPLICATE of bug 737468
Product: evolution
Classification: Applications
Component: Mailer
3.16.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-09-12 20:47 UTC by Kip
Modified: 2015-09-17 06:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kip 2015-09-12 20:47:53 UTC 
When checking for mail, I am getting the following error message multiple times a day.

Error while Filtering new messages in 'INBOX'.
Execution of filter 'Junk check' failed: Empty cache file: /home/kip/.cache/evolution/mail/1441580502.4173.2@kip-desktop/folders/INBOX/cur/13/136733

This is strange because the file in the cache is not empty, but 16K.

I have a "Junk" message filter that is there to catch what SA misses. If one of its rules is breaking, and there are many of them, there is no way to tell from this error message which rule it is.
Comment 1 Milan Crha 2015-09-15 09:53:02 UTC 
Thanks for a bug report. I suppose this is an IMAPx account. It can be that the message download failed for some reason, and the referenced file was really empty in the time of the filter run, then another request made the file properly loaded. There used to be an issue with this for the IMAPx accounts.

Since a fix for bug #745545 the internal IMAPx request processing had been made a bit more robust, also to address this particular error with message download. Please see also bug #737468, which is the same as yours. I'm marking this as a duplicate fo the later, but please note of the 'temporary' and 'workaround' words in its summary, the real fix is in the former bug report.

*** This bug has been marked as a duplicate of bug 737468 ***
Comment 2 Kip 2015-09-15 16:49:25 UTC 
Thanks Milan. I will try to reduce the number of simultaneous connection threads to one to see if it makes any difference. Do you know which version of Evolution onwards this might have been patched? I am using 3.16.5.
Comment 3 Milan Crha 2015-09-16 09:06:44 UTC 
The linked bugs at the comment #1 have the version numbers since which the changes are available, though those are development versions. The target in the stable releases is 3.18.0, to be released the next week.
Comment 4 Kip 2015-09-16 22:22:10 UTC 
Thanks Milan. I look forward to 3.18.0. In the mean time, however, I've noticed that the cache errors have disappeared since reducing the number of concurrent connection threads to one.
Comment 5 Milan Crha 2015-09-17 06:10:04 UTC 
(In reply to Kip from comment #4)
> the cache errors have disappeared since reducing the number of
> concurrent connection threads to one.

Right, that was one of the workarounds. I forgot to mention it here, I'm sorry.
Comment 6 Kip 2015-09-17 06:17:30 UTC 
No problem. Thanks again for your help. I'll let you know if 3.18.0 shows the same problem with N > 1 threads.