(*** This bug was imported into bugs.kde.org ***) Package: kmail Version: 1.3.9 (using KDE 2.9.0 2 (3.0 beta2)) Severity: wishlist Installed from: Mandrake Linux 8.1 i586 - Vitamin Compiler: gcc version 2.96 20000731 (Mandrake Linux 8.1 2.96-0.62mdk) OS: Linux (i686) release 2.4.8-26mdk OS/Compiler notes: Once in a while I'll have a message filter send a "good" message into my "Dumpster" folder. Because I have over 75 folders and 300+ filters it can be difficult (if not impossible) to figure out which of the filters triggered the problem. My proposal is to have a RMB command on a message to run filters on the message and highlight portions of the message that trigger filters. Or equally as useful a popup window that lists every reason why the message ends up where it does. In this manner I can easily resolve a problem filter. Thanks for the great work! Kmail isn't getting slower by the hour with KDE3b2. I'm in heaven :) (Submitted via bugs.kde.org) (Called from KBugReport dialog)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 22 February 2002 03:13 sean@digitalspinner.com wrote: > My proposal is to have a RMB command on a message to run filters on > the message and highlight portions of the message that trigger > filters. IMHO this is much to complicated. > Or equally as useful a popup window that lists every > reason why the message ends up where it does. In this manner I can > easily resolve a problem filter. Optional logging of filters would be quite helpful. As some information=20 is already printed via kdDebug it should be easy to redirect this info=20 into a file or to simply store it in memory. Regards Ingo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8dse4GnR+RTDgudgRAlyGAKCCPN4EPhksUmV7jbBMpW72+kgOCACgvGkn xCU6TXzS93JCMJ0cZv04NIU=3D =3DbMe2 -----END PGP SIGNATURE-----
The pop3 filters are not operating properly with my email account although= I seem to have configured them correctly. I think that the cause is failure of my email account to respond to "delete" commands and rather than any fault in kmail. It would help if I could confirm that one or more filters are triggered. The confirmation could be something as simple as a check box on eather filter configuration panel -- when checked the filter would ask for confirmation prior to executing and would show the data that had triggered the filter. If you consider this to be a useful modification I would hope to see it in= a future release. Best regards Ian
I also have desperate need of filter logging of some kind. I think anyone with more than a dozen or so filters would feel the same way... things get complicated, and it is just painful trying to figure out where a filter has gone wrong when messages end up in the wrong place. The proposal for actual highlighted analysis would put KMail well ahead of any other program... however, that does sound like a big job. I'd be very happy just for a simple filter log which lists just basic message info and the name of the filter which is triggered by it. Something perhaps like this: [timestamp] [msg_id] [msg_date] [msg_from] [filter name] [destination folder] (another thing which would be so helpful would be hierarchical filters... so you have a filter tree rather than a list... but that's another wish).
*** Bug 69951 has been marked as a duplicate of this bug. ***
Very usefull feature: It applies also on KDE 3.2.0 on Suse 9.0. If you have multiple mail accounts and filter them in different folders, sometimes you actually don't know where the mail went. In Eudora (Win32 mail client) you have a nice feature that shows in a separate window a filter report regarding where the downloaded mail went, something like: Maildir1/In 3 messages Maildir2/mailinglist 8 messages Maildir3/Mum 1 Message I think that having such a report after the mail download would be very usefull (especially when you come back from a vacation and you didn't have mail access for a bit). Regards, Timur
Logging of the filter rules evaluation and applied filter actions is implemented. It's not available in KDE 3.2.x yet, you might want to use sources from CVS or CVS snapshots. The feature will be released with the KDE PIM 3.3 release (see http://developer.kde.org/development-versions/kdepim-3.3-release-plan.html ).