Have upgraded to the latest release that also include OpenPGP
support. Its a while since looking at CipherMail and am confused
over the different triggers. From the global settings page I now
Encryption subject trigger
Force encrypt trigger
Force signing trigger
Signing subject trigger
The subject triggers will only check the subject of the email. Depending
on the configuration, the match will either be done on some static
string or a regular expression. With the subject trigger, the trigger
can be removed from the subject if enabled.
The Force encrypt and Force signing trigger can be used to trigger on
some email header with some value. This can for example be used if you
have some automated system which sends email and you want certain emails
to be encrypted. Or, if you have some plugin for your email client (for
example Zimbra) and want to enable encryption when the user selects some
So the question is, if one has S/MIME enabled, and a valid
certificate in place, how do you trigger encryption when "Encryption
Mode" is set to "No Encryption" ?
If you want to allow the user to add something to the subject which then
should trigger encryption, use the "Encryption subject trigger". If you
have some plugin which can add a header when a "encrypt" button is
pressed, you might use the "Force encrypt trigger".
If OpenPGP is enabled then will
CipherMail select based on whether the recipient supports S/MIME or
OpenPGP by checking whether a certificate is in the store ?
If the recipient has a valid S/MIME certificate and S/MIME is enabled
for the sender and recipient, the message will be S/MIME encrypted. If
not and the recipient has a trusted PGP key and PGP is enabled for
sender and recipient, the message will be PGP encrypted. For the
complete decision process, see the mail flow in the appendix of the
On 07/05/2014 10:29 AM, Phil Daws wrote:
CipherMail email encryption
Open source email encryption gateway with support for S/MIME, OpenPGP
and PDF messaging.