SUMMARY Configure KMail --> Plugins --> DKIM Checker works OK until KMail is restarted. Then it breaks. STEPS TO REPRODUCE 1. Open Configure KMail --> Plugins --> DKIM Checker Configuration dialog (click the button). 2. Make sure "Enable DKIM Support" is *not* checked; close dialog, exit KMail. 3. Restart KMail, then check the "Enable DKIM Support" option. 4. DKIM checking starts working as advertised, generally reporting either "DKIM valid" or "DKIM not signed" (when DKIM header is not present). 5. Exit KMail and restart the program. 6. Now DKIM checking is broken: every formerly valid signature is now reported to be invalid. OBSERVED RESULT DKIM Checker only works until KMail is restarted. Then it fails. The only workaround I have found is to change the configuration file ("Not Enabled"), shut KMail down, then restart KMail and change the configuration file again ("Enabled"). EXPECTED RESULT If the DKIM Checker is turned on, it should still function correctly when KMail is stopped and re-started. Something is not being initialized correctly when KMail starts up. Reconfiguring the DKIM Checker forces proper initialization once and once only. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This may be related, indirectly, to bug #204712. I hadn't even noticed this feature of KMail until recently, when I added new documentation for the "Plugins" configuration page. I discovered the bug when I was experimenting with DKIM Checker so I could write some documentation for this feature.
I can't confirm this bug. I fixed a lot of bug in 21.04 So please verify it when this release will be done. Thanjs
Maybe this isn't really a bug. There's a drop-down box in the configuration dialog for "DKIM Checker" labeled "Save Record Key". The default value is "Nothing". If I change that to "Save", or "Save and Compare", DKIM checker seems to work correctly. I'll add that little hint to the documentation (which didn't exist until recently), and close this bug report.