Hello,
I am trying to set up S/MIME encryption with a EAS synced mailbox from a
sogo 2.2.17a server on my android device (Samsung Galaxy S4, Android 5.0.1).
However, this fails with both the native client as well as "nine".
When sending a signed message, the receiving mail program displays the
message as corrupt: Message has been changed after sending, for both
clients. I assume that some change happens on the sogo server.
Sending encrypted messages always fails, as I was not able to figure out
a way to import the senders public key in neither of the two clients.
The Samsung native client tries to download the key from the server, but
fails. Nine does not give any message, just a "red" encryption sign, and
sends unencrypted.
Will S/MIME encryption be supported at some point within SOGo & EAS, or
does it already work and I just mis-configured the whole thing?
Thanks for your support!
Best,
Heiner
--
[email protected]
https://inverse.ca/sogo/lists
