Cisco Cisco Email Security Appliance C670 Guida Utente
19-8
Cisco AsyncOS 9.0 for Email User Guide
Chapter 19 S/MIME Security Services
Signing, Encrypting, or Signing and Encrypting Outgoing Messages using S/MIME
Step 3
Configure the following fields:
Step 4
Submit and commit your changes.
S/MIME Profile Name
Enter the name of the sending profile.
S/MIME Mode
Choose the S/MIME mode. Possible values are:
•
Sign
•
Encrypt
•
Sign/Encrypt. Sign and then encrypt
•
Triple. Sign, encrypt, and then sign again
Note
If you are using one of the following S/MIME modes: Sign,
Sign/Encrypt, or Triple, messages will be bounced to the sender
if the signing fails.
Sign/Encrypt, or Triple, messages will be bounced to the sender
if the signing fails.
Signing Certificate
Choose the signing certificate to use.
Note
You need to set this field only if you choose one of the following
S/MIME modes: Sign, Sign/Encrypt, or Triple.
S/MIME modes: Sign, Sign/Encrypt, or Triple.
S/MIME Sign Mode
Choose the mode of S/MIME signing. Possible values are:
•
Opaque
•
Detached
Note
You need to set this field only if you choose one of the following
S/MIME modes: Sign, Sign/Encrypt, or Triple.
S/MIME modes: Sign, Sign/Encrypt, or Triple.
S/MIME Action
Choose the action that AsyncOS must take if the recipient's public key is
not available. Possible values are:
not available. Possible values are:
•
Bounce. The message is bounced to the sender if any one of the
recipient’s public key is not available.
recipient’s public key is not available.
•
Drop. The message is dropped if any one of the recipient’s public key
is not available.
is not available.
•
Split. The message is split. The message to the recipients whose
public keys are not available are delivered without encryption and the
message to the recipients whose public keys are available are
encrypted and delivered.
public keys are not available are delivered without encryption and the
message to the recipients whose public keys are available are
encrypted and delivered.
Example: Assume that you are sending a message to
bob@example1.com and dave@example2.com and the public key of
dave@example2.com is not available. In this scenario, if you have
selected Split, AsyncOS will:
bob@example1.com and dave@example2.com and the public key of
dave@example2.com is not available. In this scenario, if you have
selected Split, AsyncOS will:
–
Deliver the message to bob@example1.com after encrypting it.
–
Deliver the message to dave@example2.com without encrypting
it.
it.
Note
You need to set this field only if you choose one of the following
S/MIME modes: Encrypt, Sign/Encrypt, or Triple.
S/MIME modes: Encrypt, Sign/Encrypt, or Triple.