Specify the use of e-mail signing or encryption
$email_security node keyword [keyword ...]
This command specifies which signing or encrypting processes will be performed on the system. The use of this command is only valid when the E-Mail Security license option is present in your license.
The parameters on this command are used as follows:
| node | the nodename of the machine which is to send signed/encrypted e-mail, or * for all nodes. This parameter is ignored by the E-Mail to Fax Gateway. |
| keyword | one of the following keywords: |
| SMIMEencrypt | the system will allow S/MIME encryption for outbound e-mail. |
| SMIMEsign | the system will allow S/MIME signing for outbound e-mail. |
| DKIM | the system will allow DKIM signing for outbound e-mail. The keyword 'domainkeys' is a synonym for this option. |
| decodeSMIME | the CopiaFacts SMTP Gateway will allow decryption of encrypted incoming messages. Messages which are S/MIME signed are always verified, but if the signature has been applied before encryption it will not be verified unless this keyword is used. |
| verifyDKIM | the CopiaFacts SMTP Gateway will allow verification of DKIM signed messages. |
| implicitTLS | enables the second SMTP server in the CopiaFacts SMTP Gateway for Implicit TLS. This should only be used in special circumstances. |
There is more information on e-mail security in the E-Mail Security and Gateway E-Mail Security topic.
An individual outbound e-mail transaction is signed and/or encrypted when the appropriate $email_options keyword is given and suitable variables are defined to specify the key file and options.
Default: none. E-Mail will not be signed or encrypted.
Examples:
Sending signed and encrypted e-mail:
$email_security * SMIMEencrypt SMIMEsign
Receiving encrypted e-mail:
$email_security * decodeSMIME
Both:
$email_security * SMIMEencrypt SMIMEsign decodeSMIME
