GNOME Bugzilla – Bug 769412
Execution of the filter 'Junk check' failed due to empty cache file
Last modified: 2016-08-08 14:07:13 UTC
Hello, I'm on Fedora 24 and sometimes I have this message in Evolution "Execution of the filter 'Junk check' failed...". It seems to be an "old" bug but it was not fixed https://bugzilla.redhat.com/show_bug.cgi?id=1177719 I don't have the full error message right now but as soon it happen again I will copy / paste it. It will be in French but I will try to translate it. If you need more infos just tell me what should I do. Thanks !
It didn't take long for this message to show again ! "L'exécution du filtre « Junk check » a échoué : Fichier de cache vide: /home/jeremy/.cache/evolution/mail/***/folders/INBOX/cur/27/9263" "Execution of filter 'Junk check' failed: Empty cache file: /home/jeremy/.cache/evolution/mail/***/folders/INBOX/cur/27/9263"
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of bug 769011 ***
If I understand you need a complete log ? If that's right how can I do this ? Thanks !
I was looking for a complete log of the snippet the user at the other bug provided. You can capture the log for an IMAPx account by running evolution as this: $ CAMEL_DEBUG=imapx evolution &>log.txt Ideally if the evolution runs in an English locale, which you can ensure by running this command before the log capture: $ export LANG=C Please make sure you'll not expose anything private in the log, as it logs also raw communication between the client and the server, including any downloaded messages. If you are unsure, then feel free to send the log only to me, to my bugzilla address, and reference the other bug report in the message Subject, thus I'd not overlook it in my spam folder. Also, in case you've defined more IMAPx accounts in the evolution, ideally disable all but the account where you can reproduce the issue, thus the log will not have interleaving communication from two servers, thus making it very confusing when reading it.