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 272411 - spam checking really CPU hog
spam checking really CPU hog
Status: RESOLVED NOTGNOME
Product: evolution
Classification: Applications
Component: Mailer
2.2.x (obsolete)
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on: 269098
Blocks:
 
 
Reported: 2005-02-09 18:40 UTC by Hubert Figuiere (:hub)
Modified: 2013-09-13 00:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hubert Figuiere (:hub) 2005-02-09 18:40:45 UTC
Spam checking is really CPU hog. I use a G3/400 laptop, and check spam for
1 message takes 15 to 20 seconds and hog the CPU to 100%

In comparison Thunderbird seems to be really instant, and it does not hog
the CPU.

I think that use of SpamAssassin has a lot to do with it.
Comment 1 Jeffrey Stedfast 2005-02-09 18:42:42 UTC
yea, I think the blame is spamassassin as well. because of that, I
dunno what to do about it.
Comment 2 Hubert Figuiere (:hub) 2005-02-09 18:48:05 UTC
bogofilter ?

That is what Thunberbird integrated.

Writing a spamc/spamd for bogofilter could be a route to follow.
Comment 3 Jeffrey Stedfast 2005-02-09 18:54:36 UTC
you could do that on your local machine. we can't simply switch to
bogofilter for all the users out there already depending on spamassassin.
Comment 4 Hubert Figuiere (:hub) 2005-02-09 18:59:44 UTC
what about new users ?

what about users that want to switch ?
Comment 5 Rodney Dawes 2005-02-09 22:55:26 UTC
The spam stuff really needs to be plug-in-ized so that people who want
bogofilter or something else, can just write a plug-in, and hook up to
appropriate signals to learn messages as ham or spam. Spamassassin is
a good default though, as it does a lot more than just simple bayesian
scoring.
Comment 6 Joaquin Cuenca Abela 2005-02-21 18:28:18 UTC
I don't understand how Spamassassin is a good default. If it is
responsible from the long time it takes to mark a mail as junk/not
junk, then spamassassin is unusable on a Desktop, no matter how good
are its other fancy features.

This single bug forced me to switch to Thunderbird, as evolution was
taking ages to just retrieve my mail and marking it as junk/not junk.
Comment 7 Not Zed 2005-02-22 04:43:05 UTC
i agree, i think using spamassasin as the default (and only) was a bad
choice, by someone who doesn't work on evolution anymore at that.
Comment 8 Not Zed 2005-05-19 10:00:59 UTC
workaround: use your own spam filtering

spamassasin has performance problems, but they are beyond our control
Comment 9 Hubert Figuiere (:hub) 2005-05-19 12:09:44 UTC
Evolution does not allow to use anything else as SpamAssassin is hardcoded.

And you probably don't realize that most people have NO control on their mail
server.

I think that closing this bug is plain wrong, whatever.
Comment 10 Matt Dew 2005-06-13 20:35:23 UTC
I agree with Rodney Dawes.  Allow for plugins.   Default it to spamassassin if
you wish, but allow others to use something else.

I work at a company that has linux desktops and a large percentage of those
desktops use Evolution, as it does have some really nice features.   Believe it
or not though, this one complaint has made several people switch to Thunderbird.

Please do not mark this as resolved. I still consider this a bug and from
reading this previous posts, I am not alone.
Comment 11 Bastien Nocera 2005-10-25 22:49:45 UTC
Just a note, bug #269098 took care of the junk filter plugin, and it should be
pretty easy to create a filter based on bogofilter/<insert preferred spam filter
here>.
Comment 12 André Klapper 2005-11-30 23:42:26 UTC
plugins are now possible and i saw a posting on the list from mikhael who has
implemented a bogofilter plugin. seems like it is only blocked by bug 313096.
Comment 13 Lionel Dricot 2006-01-07 22:40:22 UTC
From an user point of view, I must say that I perfectly agree with Joaquin Cuenca Abela. It not only a plugin that's needed : it's a good default !

Most users doesn't change the default config.
Comment 14 vgrebenschikov 2006-06-01 11:27:25 UTC
Please add bogofilter plugin (bf-junk-plugin) in default evolution distribution.
Also ability to select junk filter plugin(s) from GUI is also very desirable.
Comment 15 André Klapper 2008-02-29 07:19:53 UTC
different junk filter plugins can be selected in the UI nowadays.
Comment 16 Srinivasa Ragavan 2008-02-29 09:57:55 UTC
I feel this bug status still holds right. It is not in Evo/GNOME's control. But speed up of Evo's junk filtering is something that is taken care. You can use Bogofilter/SA or server side headers etc.
Comment 17 Hubert Figuiere (:hub) 2008-02-29 12:59:44 UTC
I always thought that this bug status should be "FIXED" only when the default spam filter would be something that made more sense than CPUAssassin. Even the Evo developer acknowledged it was a poor default choice. Now that there is a bogofilter plugin, it should be easier to really fix.

Default choice always matter, because most users will not change it. So the default choice should do the right thing(tm)