Bug 79181

Version:            (using KDE KDE 3.2.1)
Installed from:    Compiled From Sources

In short: after installing kmail and kmail-crypto (and maybe enabling the plugin) I should just be able to at least view and check S/MIME signatures and also have some GUI to install my own certificates for signing and/or encryption.

Longer: I spent 3 hours trying to get S/MIME support in kmail running - using instructions from AEgypten pages - and failed (currently gpgme-openpgp.so crypto plugin seems to work but gpgme-smime.so reports that it has not been initializated without any further details and I have absolutely no idea what I can try to resolve it). And I am experienced Linux programmer and administrator (although without special knowledge about S/MIME itself). I can't even imagine 'normal user' to try...

In my opinion the whole crypto-plugin thing should be organized so:

1) Whatever can be performed automatically during an installation, should be done (things like reconfiguring X-session to run gpg-agent, generating sample certificates, initializing certs database etc).

2) To activate the crypto-plugins, the user should set some checkboxes or select from the list instead of guessing what libraries are there and how they are named (of course some 'Other...' option for non-typically installed plugin could be present). The simplest solution: all plugins found in typical places are just visible in configuration window, they are just initially disabled.

3) When the user attempts to enable such a plugin, the whole rest of the initialization should happen. The user should be queried all the info kmail crypto needs to work and assisted in efforts like installing the existing certificate or buying one. The main point is that one should be able to configure everything one needs to have S/MIME working without running any openssl command manually.

4) In case bugs happen, there should be detailed error report.