Deployment scenarios for outgoing email

The following examples demonstrate how encryption and signing can be deployed on email messages sent to partners.

ClosedSign email using Secure Email Gateway

User sends plain text message, Gateway delivers signed message.

For more information, see Define an automatic mail signing endpoint.

ClosedSend PGP or S/MIMEClosed Secure Multipurpose Internet Mail Extensions (S/MIME) is a specification for secure email messages that uses the X.509 format for digital certificates and uses various encryption algorithms such as 3DES.-encrypted email to a partner

User sends plain text message, Gateway encrypts message using corporate or recipient's key.

For more information, see the following topics:

ClosedSend encrypted email to a recipient with no PGP or S/MIME capability

User sends plain text message, Gateway encrypts message using password.

For more information, see Define a password encryption endpoint.

ClosedDeliver content-checked email in the original encrypted message

User sends encrypted message, Gateway decrypts, checks content, and then delivers original encrypted message.

  1. Configure the policy route to decrypt and check content.

    See Enable encryption or decryption on a policy route for more information.

For more information, see Original Encrypted Messages default settings.

ClosedDeliver content-checked email in a re-encrypted message

User sends encrypted message, Gateway decrypts, checks content, and then delivers re-encrypted message.

  1. Configure the policy route to decrypt and check content.

    See Enable encryption or decryption on a policy route for more information.

ClosedDeliver unmodified encrypted message

User sends encrypted message, Gateway delivers original encrypted message.