[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 52192] using spamassassin as filter blocks kmail
From:       Alexander McCormmach <alexander () tunicate ! org>
Date:       2003-04-03 9:03:07
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=52192     




------- Additional Comments From alexander@tunicate.org  2003-04-03 11:03 -------
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!
[prev in list] [next in list] [prev in thread] [next in thread]