Please be so kind and explain the behavior of emClient to me:
I have set up two email addresses in emClient.
Email address: (example name) [email protected]. I have stored an S/MIME public key for this address under "Certificates/Keys of Others".
Email address: (example name) [email protected]. There is no encryption technology stored for this address.
I am now unable to send an encrypted email from [email protected] to [email protected].
Error message: No S/MIME certificate was found for [email protected].
Why does the sender [email protected] need their own S/MIME certificate?
From my understanding, the sender only needs the encryption information for the recipient ([email protected])
Technically, you only need the public key for the recipient of the message (X) or course, but eM Client also encrypts the copy of the message that is stored in the sender’s (Y) Sent folder, so that is why it’s trying to find a public key for (Y) as well.
The idea behind this design in eM Client is that if you need to keep the content of the message secret when sending it, you would probably not want an unencrypted copy of the same message in your Sent folder that anyone could read.
Hello Olivia,
that’s understandable.
Now, if I send an email from X to Y, the email is sent unencrypted. Now, according to your explanation, I would have an encrypted message in X’s SENT folder. But the sent message is only signed. I would have expected the “lock” symbol behind the sent message.