|
$email_sign_keyfile [FS] |
  
|
|
$email_sign_keyfile [FS] |
|
Specify File containing S/MIME Signing Key
$email_sign_keyfile "pathname[;passphrase]"
$email_sign_keyfile WINDOWS
$email_sign_keyfile "listfile.lst"
This command is used to supply a key or keys for S/MIME signed e-mail. It is a required command for an FS file which also includes an $email_options keyword of SMIMEsign.
The parameters on this command are used as follows:
| pathname | The full pathname of a file containing the sender's public and private keys (normally a .PFX file) |
| passphrase | The passphrase for the keyfile (normally required). |
| windows | This keyword causes the 'my certificates' section of the Windows certificates store to be searched for a certificate corresponding to the From: header e-mail address in the mail item. This requires that the certificate is imported into the system certificate storage with protected mode disabled; if not, there will be a prompt for confirmation on the first occasion on which the certificate is accessed after starting COPIAFACTS. Note that this property cannot be changed after a certificate has been imported. |
| listfile | The command may specify a pathname of a file with extension .LST which contains one or more lines with the format: |
keyfile1;passphrase1
keyfile2;passphrase2
...
Using the listfile form of the command avoids the need to have the passphrase visible in every FS file.
One of the keyfiles, however specified, must contain a key which is associated with the e-mail address which is specified on the $email_from command in the same FS file. Using multiple keyfiles allows the list to be shared for various From: addresses, but is less efficient than specifying a single keyfile tied to an individual From: address. If no match is found for the From: address, the e-mail transmission will fail.
Examples:
$email_sign_keyfile "`FFBASE\mykeyfile.pem"
$email_sign_keyfile "`FFBASE\keyfile.pfx;xyzzy"
Topic url: http://www.copia.com/support/refmanual/index.html?%24email_sign_keyfile.htm