http://bugzilla.opensuse.org/show_bug.cgi?id=1185855 Bug ID: 1185855 Summary: dkim filter extension in Kmail fails to work correctly with spamassasin (spamd daemon) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: stakanov@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Go to the 5.17.0 version of kmail. The following applies when activating dkim extension in kmail, provided you are using spamd daemon with spamassasin (I did not verify the scripted version). The new mails will be correctly identified as dkim compliant, or not. Fair enough, this is the purpose. BUT, the usability is greatly reduced in case you have old mail inside a local folder or even a imap account with old mail. The old mail (as at the time there was no dkim will ALL be signed as spam and put into the trash. Once aware of it you may the instinct to select all messages and sign them as "Ham". Then to replace them into the inbox. Unfortunately, after few minutes you find them again signed as spam in the trash. So: DKIM check estension works for new DKIM compliant mail. When no DKIM is present mail i set as spam. But when mail has been wrongly classified as spam, then even if manually restored and then signed explicitly as HAM (I refer particularly to older so to say "historical mail") this is not honored by spamd daemon and the mail is trashed again. The described behavior stops immediately when the DKIM verification plugin is deactivated in the extension. What the software should do: verify new mail on DKIM compliance. What the software should also do: honor the manual settings as "no spam / ham, once the user provides this information. Any further check of DKIM of such a message should NOT trigger trashing as spam. -- You are receiving this mail because: You are on the CC list for the bug.