Bug 98765

Summary: Filter logging is deactivated everytime KMail is restarted
Product: [Applications] kmail Reporter: tobias
Component: filteringAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: wishlist CC: bjoern, KaiUweBroulik2, kde.20.danlex, montel, orbert
Priority: NOR    
Version: 1.7.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description tobias 2005-02-07 13:08:28 UTC 
Version:           1.7.2 (using KDE 3.3.2 Level "a" , unofficial build of SUSE )
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.8-0-default

Filter logging is deactivated when you exit and restart Kmail.
Comment 1 Andreas Gungl 2005-02-08 22:34:18 UTC 
The behavior is intended. So let's make it a wish. BTW, I've also thought about it, but it probably won't make it into KDE 3.4.
Comment 2 Robert Morrison 2006-01-03 20:00:57 UTC 
Reason for change: I think the typical use case for this facility
is when a user observes that filters are not behaving as expected.
The log is turned on to help debug. At that moment, though, a user
typically cannot 'requeue' the messages that were not filtered as
expected; the user must wait for more. Since most messages arrive
in the morning, for most users this means that a kmail restart is
involved. But if the user does not remember to turn the filter log
back on before fetching mail, the opportunity to capture data is lost.

There is already a log size limiter in place, so disk space is
not an issue.

Final note: this need not be an either/or proposition. If users
want both behaviors, a subordinate checkbox labeled something
like "retain this setting next time kmail starts" could be added.
Comment 3 Andreas Gungl 2006-01-03 20:26:06 UTC 
*** Bug 119251 has been marked as a duplicate of this bug. ***
Comment 4 Thomas McGuire 2008-03-02 23:12:20 UTC 
*** Bug 158680 has been marked as a duplicate of this bug. ***
Comment 5 Kai Uwe Broulik 2010-09-05 16:11:26 UTC 
Yes, really annoying, I don‘t know if you have to choose “save as” to spcify a saving location for the log but if you had to do that, it‘d really stupid.
Comment 6 Laurent Montel 2012-02-24 16:35:44 UTC 
Fixed in 4.8.1