Version: 4.8 (using KDE 4.8.0) OS: Linux As spamd has not been detected as the default antispam filtering method, once trying to tag any new email messages as spam or ham, KMail2 deletes them just after a few seconds. Reproducible: Always Steps to Reproduce: Right click on a new message>>Apply filter>>Classify as spam or Classify as ham Actual Results: The message is being deleted. Expected Results: The message has to be tagged as spam or ham.
I don't understand how you can have these filter if you don't have spam program ? could you paste your filter configuration for these 2 filters please ?
(In reply to comment #1) > I don't understand how you can have these filter if you don't have spam program > ? > > could you paste your filter configuration for these 2 filters please ? Laurent, I've never said spam program hasn't been installed: it's up and running many years now... :-) The problem is about the "Classify as ham" filter; I will translate it from Italian: - Verify all criteria: Byte dimension => 0 byte; Filter actions: - Classify as >> ham; - Execute command >> sa-learn -L --ham --no-sync --single; - spamassassin -d.
configurate filter->export filter => select all filter which define spam etc. => save it paste config here please
(In reply to comment #3) > configurate filter->export filter > > => select all filter which define spam etc. > => save it > paste config here please This is the content of the file /etc/mail/spamassassin/local.cf: [# This is the right place to customize your installation of SpamAssassin. # # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # tweaked. # # Only a small subset of options are listed below # ########################################################################### # Add *****SPAM***** to the Subject header of spam e-mails # # rewrite_header Subject *****SPAM***** # Save spam messages as a message/rfc822 MIME attachment instead of # modifying the original message (0: off, 2: use text/plain instead) # # report_safe 1 # Set which networks or hosts are considered 'trusted' by your mail # server (i.e. not spammers) # # trusted_networks 212.17.35. # Set file-locking method (flock is not safe over NFS, but is faster) # # lock_method flock # Set the threshold at which a message is considered spam (default: 5.0) # # required_score 5.0 # Use Bayesian classifier (default: 1) # # use_bayes 1 # Bayesian classifier auto-learning (default: 1) # # bayes_auto_learn 1 # Set headers which may provide inappropriate cues to the Bayesian # classifier # # bayes_ignore_header X-Bogosity # bayes_ignore_header X-Spam-Flag # bayes_ignore_header X-Spam-Status # Some shortcircuiting, if the plugin is enabled # ifplugin Mail::SpamAssassin::Plugin::Shortcircuit # # default: strongly-whitelisted mails are *really* whitelisted now, if the # shortcircuiting plugin is active, causing early exit to save CPU load. # Uncomment to turn this on # # shortcircuit USER_IN_WHITELIST on # shortcircuit USER_IN_DEF_WHITELIST on # shortcircuit USER_IN_ALL_SPAM_TO on # shortcircuit SUBJECT_IN_WHITELIST on # the opposite; blacklisted mails can also save CPU # # shortcircuit USER_IN_BLACKLIST on # shortcircuit USER_IN_BLACKLIST_TO on # shortcircuit SUBJECT_IN_BLACKLIST on # if you have taken the time to correctly specify your "trusted_networks", # this is another good way to save CPU # # shortcircuit ALL_TRUSTED on # and a well-trained bayes DB can save running rules, too # # shortcircuit BAYES_99 spam # shortcircuit BAYES_00 ham endif # Mail::SpamAssassin::Plugin::Shortcircuit]
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.
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.