Specify File containing S/MIME Signing Key
The parameters on this command are used as follows:
|pathname||The full pathname of a file containing the sender's public and private keys. The file extension and format must be .PFX, .P12 or .PEM.|
|passphrase||The passphrase for the keyfile (normally required). You may use one of the SECRETx variables for this purpose, to avoid having to place the passphrase in clear in the FS file. Unlike in an infobox file, this usage of the secret variable cannot currently be authenticated, because authentication would not survive the rewriting of the FS file. There must be no spaces on either side of the separating semicolon.|
|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:|
Using the listfile form of the command is another way to avoid having 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. If no match is found for the From: address, the e-mail transmission will fail.