GNOME Bugzilla – Bug 323630
hide Junk UI if Junk plugin is not enabled
Last modified: 2006-01-16 01:24:52 UTC
Please describe the problem: The junk filter is not filtering out junk mail or spam from my inbox. Steps to reproduce: 1. Setup a normal POP account 2. Check both boxes in Edit-> Preferences-> Mail Preferences-> Junk 3. Check for new messages Actual results: I get all the mail to my inbox including junk and spam. Expected results: I would expect that the junk and spam would go to their applied folder, "junk" Does this happen every time? Yes Other information: No
hi lyf, please make sure that SpamAssassin is installed and the sa-plugin enabled (see "Edit | Plugins"). quoting guenther from here on: "Also, SpamAssassins built-in Bayes filters need to be trained. The default SA rules work from the very first message, as do the network tests. Bayes needs to learn 200 Spam and Ham /each/, before kicking in (default install). Note: "Learn", not identify. Messages are learned either by manually classifying them, or if a certain threshold is reached (which is more extreme than the line between Spam and Ham)."
I have the same problem on Debian and Ubuntu, after an upgrade from 2.2 to 2.4. I don't have any Edit/Plugins menu entry. If a plugin is needed and not active or not present, Evolution shouldn't display the junk/not-junk buttons, or should warn the user that they're not working.
Okay, the Edit/Plugins item appears when you install plugins, and everything works fine afterwards. However, the graphical interface needs to be fixed to hide inactive buttons or warn the user.
rephrasing
This bug covers more than one bug. According to the summary (hide UI if disabled), this bug is a duplicate of bug 259506. Warning the user and/or getting rid of the UI if the plugin does not work is covered in bug 273041. If you seriously thing, those other bugs don't cover the topics raised in here, feel free to reopen this bug. Thanks for taking the time to report this issue! BTW, the separate evolution-plugins package is a Debian/Ubuntu specific issue. You are not the first one who got bit by this... *** This bug has been marked as a duplicate of 259506 ***