Version: 1.6 (using KDE 3.2.0, Mandrake Linux Cooker i586 - Cooker) Compiler: gcc version 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk) OS: Linux (i686) release 2.4.21-0.13mdk The POP filtering doesn't work "out of the box" when an user doesn't know how to set it the odd way. An user has to do this now : 1) set on mail filtering with min. size of 1 bytes for an account 2) set a first POP filter to delete any message on server containing e.g. word "money" as subject of a message 3) set a second POP filter to download all messages with any header matching e.g. regular expression ".*" and move it down as the last filter it would be much nicer when the POP filters were applied first together with the corresponding action (e.g. deleting the matched mail on the server) regardless on the mail size filtering option is set on or off, the second could be applied that mail size filtering (if any) and as the third go the local filters. luci
I was stuck trying to use POP filters, as this bug compromises the usability of this feature. I would suggest to implement the option as "use POP filters with this account" (regardless of message size), and then leave it marked by default when creating new accounts. The user could then implement her own filter to handle large messages.
>3) set a second POP filter to download all messages with any header matching e.g. regular expression ".*" and move it down as the last filter This is the part I would NEVER have found out myself, I think it is a stupid requirement. You do not have to do a similar thing for normal filters. Please make this a default filter.
*** This bug has been confirmed by popular vote. ***
Wow, I just wanted to file a bug report about the completely broken pop filtering. (Deleting messages with a specified From never worked...) The current behaviour seems to be just crazy. First of all, filtering shouldn't be tied to some non-related option in the account settings. Second, the default action should be to let the message pass, i.e. download it. The only thing required to just delete mails coming from some specific address (or having the subject match some regexp) should be that rule and nothing else.
same as with bug 64777 any progress on this ?
*** Bug 64777 has been marked as a duplicate of this bug. ***
*** Bug 137575 has been marked as a duplicate of this bug. ***
this beast still alive ?
*** Bug 74888 has been marked as a duplicate of this bug. ***
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.