Version: 1.5.94 (using KDE 3.1.94 (CVS >= 20031206), compiled sources) Compiler: gcc version 3.3.3 20040110 (prerelease) (Debian) OS: Linux (i686) release 2.4.24 I'm using filter to teach spam to spamassassin - pipe through "sa-learn --spam" and move to trash. If I apply it to the message in inbox, filter works correctly, but after move I still see this mail in message panel and in message list no message is selected, so I have to press arrow to select next message. Just moving messages to another folder works correctly, it seems to be problem only if move is initiated from filter.
I could not reproduce the problem. Please reopen the report if you find a way to make this still happen.
Please reopen this bug, as it's not solved. If not, I'll report another one. Thanks.
On Thursday 29 July 2004 11:54, LuisMi GarcXXa wrote: > Please reopen this bug, as it's not solved. Please note that there are different way to trigger filters. In KMail 1.7 (KDE 3.3) there is "Apply Filter (Ctrl-J)" and "Apply Filters (submenu)". If you refer to the first (i.e. Apply Filter), then you can reopen this bug if you can tell me how to exactly reproduce the problem. If you refer to the second (i.e. Apply Filters - ...), then please note that report #75517 describes this problem in more detail and is used as a reference for duplicate reports. > If not, I'll report another one. Do you call that polite?
I wasn't trying to be unpolite. English is not my tongue mother, so sorry if I miss-explained myself. I was meaning that if nobody read that comment or nobody reply, I'll fill another bug for calling your attention. Just writed that too fast without re-reading it. Sorry, no mean to be un-polite. Now for the bug: I (and I think the reporter) don't mean that "Apply Filter" thing. We means that when you click the button "Classify As Spam" (you must have created it throught Spam Wizard), the message gets moved to spam folder, but the message view pane don't get updated. It will continue showing the spam message we just "marked and moved" to spam folder. I don't know if that can be understood, because my english is very bad. If not, please tell me and I'll do Try #3. Thanks and cheers.
On Thursday 29 July 2004 16:25, LuisMi GarcXXa wrote: > I (and I think the reporter) don't mean that "Apply Filter" thing. We means > that when you click the button "Classify As Spam" (you must have created it > throught Spam Wizard), the message gets moved to spam folder, but the > message view pane don't get updated. It will continue showing the spam > message we just "marked and moved" to spam folder. Well, this is exactly what report #75515 describes, because the toolbar button triggers the appropriate menu item below "Apply Filters". (You are right, that button is usually created by the wizard.) I've closed this report because the so called ad-hoc filters didn't exist when the report was written. So this report certainly meant a temporary "Apply Filter" bug which is no longer reproducible. Please consider voting for #75517.
Ühel kenal päeval (neljapäev, 29. juuli 2004 17:37) kirjutas Andreas Gungl: > I've closed this report because the so called ad-hoc filters didn't > exist when the report was written. So this report certainly meant a > temporary "Apply Filter" bug which is no longer reproducible. "Apply filter" submenu exists for sure in kmail 1.6 and it existed in kmail 1.5.94 (it's pre 1.6), which I used to write this report, as well. And that's exactly what I meant with this report.
On Thursday 29 July 2004 17:06, Hasso Tepper wrote: > "Apply filter" submenu exists for sure in kmail 1.6 and it existed in > kmail 1.5.94 (it's pre 1.6), which I used to write this report, as > well. And that's exactly what I meant with this report. So please reopen the report and mark it as duplicate of 75517 (or I'm gonna do it tonight - can't do so in the moment). Andreas
Reopening after discussion with the original reporter - actually I had recommended to reopen it after describing a way to reproduce. Too bad that we talked about different things when we meant "applying a filter", seems like the description was not enough in detail. Nevertheless I'm going to mark it as duplicate of #75517 because that subject is more clear for the developers. Anyway, reporters will find this report as well and see the duplicate relation.
*** This bug has been marked as a duplicate of 75517 ***
fixed in cvs. Thanks.