Bug 284405 - filter not used at reception+use after without attachment
Summary: filter not used at reception+use after without attachment
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 20:20 UTC by Daniel Moyne
Modified: 2017-01-07 21:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Moyne 2011-10-18 20:20:10 UTC
Version:           1.99.0 (using KDE 4.7.2) 
OS:                Linux

some messages received were detected as "unsure" by bogofilter with addition of "???UNSURE???" in subject (configuration of bogofilter) ; my last filter designed as follows  :
if (subject contains "???UNSURE???") do {
remove X-Bogosity in header
remove X-Attachment in header
move in folder Dossiers Locaux/Bogofilter/unsure
}
was not executed as message were left in "boîte de réception".

Later on the message was properly processed but in some cases the attacments were discarded in other cases no (all the serie of messages contained attachments)
}

Reproducible: Didn't try

Steps to Reproduce:
I need to ask the sender to resend some of the messages where tha attachments were lost ; this time I will fiter the sender e-amil address to move directly the messages in a proper folder

Actual Results:  
filter properly executed at reception not at second opening of kmail

Expected Results:  
in such case all the messages should have been placed in Dossiers Locaux/Bogofilter/unsure including attachments (here *JPG files) though some of the messages kept their attachments

OS: Linux (x86_64) release 3.0.0-12-generic
Compiler: gcc
Comment 1 Denis Kurz 2016-09-24 17:54:25 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:49:32 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.