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 766378 - spam filtering hangs fetching mail
spam filtering hangs fetching mail
Status: RESOLVED DUPLICATE of bug 746276
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2016-05-13 14:32 UTC by chernoff
Modified: 2016-05-16 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace of all threads (74.67 KB, text/plain)
2016-05-13 14:32 UTC, chernoff
Details

Description chernoff 2016-05-13 14:32:47 UTC
Created attachment 327795 [details]
backtrace of all threads

Evolution hangs while fetching mail from a POP server when spam assassin filtering is turned on. Disabling the filtering leads to expected results. 

Killing evolution with force-shutdown must leave things in a unsatisfactory
state since (sometimes) the mail that is being fetched is lost and (sometimes) the passwords are forgotten.

(I have also noticed problems trying to use bogofilter. In this case there are truncated addresses left in the Inbox, probably one for each lost piece of mail.)

In both cases (spam assassin and bogofilter) I see quick messages about unknown background operations flashing between things like updating the spam database.

In mail preferences -> junk I have CHECKED:

check incoming messages for junk, 
check custom headers for junk, 
do not mark messages as junk if sender is in my address book, 
lookup in local address book only, 
and include remote tests
Comment 1 Milan Crha 2016-05-16 14:22:11 UTC
Thanks for a bug report and the backtrace. I see from that that the evolution is stuck waiting for an address book to be opened. It's not fully correct, there was some issue with it, which had been addressed within bug #746276. The final fix from there didn't make it into yours 3.12.11.

Either ask your distribution maintainers to include the patches from that bug report in the distribution, or update to more recent evolution (the current upstream stable version is 3.20.2), or turn off "do not mark messages as junk if sender is in my address book" in the Junk tab of the Preferences, which will stop lookups for the address books, thus also will not get stuck. The last this is more like a workaround, it would be better to apply the fix for it, rather than the workaround.

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