Thank you for your answer, but i can’t generate S/MIME cert on eM Client, it only generates PGP cert, and i have to use S/MIME cert to mailing with clients.
I’m creating my own cert with OpenSSL as below;
First creating x509 formatted .csr and sign it under Root Ca.
After that, i convert that created cert to .p12 format.
It should work i suppose, because it is the default procedure.
All my keys were brought over from Linux and work just fine. I have one S/MIME that I use regularly for signing, but the others are all either Open PGP or a few PGP generated by eM Client.
Maybe there was something when you created and converted the certificate that makes it incompatible with eM Client.
If you have a Pro License, best bet would be to open a support ticket directly with eM Client. I am sure they will be able to assist you further. If you are just evaluating the application, then unfortunately there is not really any support contact directly with them.
Experiencing the exact same issue. Three of my S/MIME keys work fine and were generated on the same machine, app, and format. My most recent key, generated today in the duplicate fashion to the other three , is providing the same error as the OP. Edit: Verified I am fully updated on the client and no change.
Hi there, sorry I was unclear. All keys were generated outside of EM Client, (Kleopatra-generated), but only my most recent one for my personal domain won’t function in the same manner as my gmail, outlook, protonmail keys. Anything I else I can provide?
Update: I’ve created a new keypair (RSA:4096) in EM CLient for my email account and I’m still getting the previously stated error message as well. Not sure if that helps. If you have an ftp or Dropbox I can zip up some data if that helps. The account is brand new so there’s nothing crucial about exposing these keys.
Update #2: It just occurred to my that the Free version of EM-Client only supports two addresses and I’ve been trying to use a third. I’m not sure if that is part of the issue but I’m upgrading to Pro to verify.
Update: I’m still in a trial mode at present so it allows more than 2 Inboxes. Whether 100% of functionality is available in Trial is unknown. ( I have purchased licences but wanted to see if this issue could be resolved before I bypass it with $$$).
I’ve modified system dates/times in an attempt to force the app to exceed the trial alotment, but there’s been no change in the resulting “There is no valid signing certificate” error. I’ve also replicated this error on two other systems.