Summary: | using spamassassin as filter blocks kmail | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Ferdinand Gassauer <gassauer> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | alexander, andre, felix.seeger, mss, rooot, stephane.nicolas |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ferdinand Gassauer
2002-12-22 17:09:04 UTC
correction : ... should be nonblocking...!!! Subject: Re: New: using spamassassin as filter blocks kmail It's unwise to pipe all incoming messages through spamassassin (I also did this when I first setup sa). It's much better to first check for mail from mailing lists, then for mail from known senders (like your friends and colleagues) and only then pipe all remaining messages through spamassassin. This will greatly reduce the time that's needed to filter the incoming mail and will make it much less annoying that KMail blocks while spamassassin checks the messages. Subject: Re: using spamassassin as filter blocks kmail On Sunday 22 December 2002 18:15, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=52192 > > > > > ------- Additional Comments From kloecker@kde.org 2002-12-22 18:15 ------- > Subject: Re: New: using spamassassin as filter blocks kmail > > It's unwise to pipe all incoming messages through spamassassin (I also > did this when I first setup sa). It's much better to first check for > mail from mailing lists, then for mail from known senders (like your > friends and colleagues) and only then pipe all remaining messages > through spamassassin. This will greatly reduce the time that's needed > to filter the incoming mail and will make it much less annoying that > KMail blocks while spamassassin checks the messages. Thanks Yes you are rigth of course, I just followed the instructions http://kmail.kde.org/tools.html without thinking of this. May be you can add this hint there cu ferdinand I just experienced the same with kde 3.0.5a. What makes me wonder is that kmail itself eats up all the processor time. Shouldn't it just wait for SA to finish it's job? I experience the same problem with SA 2.50-cvs. A workaround is to start KMail with nice -5. I'll try to check what KMail 3.1 says this weekend. *** Bug 49578 has been marked as a duplicate of this bug. *** Forgot about this bug; it's still happening in 3.1. Anybody working on making the filters asynchronous? Subject: Re: using spamassassin as filter blocks kmail AFAIK currently nobody is working on this. *** Bug 56776 has been marked as a duplicate of this bug. *** Ah, I am sorry for not catching this bug report which is certainly a duplicate of mine. Still, it just seems like, theoretically, any filter-activated program could take a very very long time to finish, even for legitimate reasons, depending on what it was designed to do--so it doesn't make much sense for KMail to stall while such a program runs to completion, does it? How difficult would it be to run the whole mail checking/filtering in a background thread? ... I would try to do this myself except I have no experience coding for KMail, and wouldn't know where to look first. On this note, do any of the more experienced KMail developers have any advice as to how a person like myself, a reasonably experienced C++ programmer (e.g. have used Qt quite a bit and some of the kdelibs), should start to figure out the massive codebase that is KMail? ... so that I could start solving my own problems... ;-) Thanks for any suggestions! *** Bug 56794 has been marked as a duplicate of this bug. *** *** Bug 58561 has been marked as a duplicate of this bug. *** I think this is some sort of duplicate of Bug 41514 with title "KMail freezes the UI when checking for new mail"... *** This bug has been marked as a duplicate of 41514 *** |