Configure encryption options for S/MIME-protected messages

You can configure encryption options to control how the BlackBerry Enterprise Server processes S/MIME-protected messages.
  1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > Email.
  2. Click the instance that you want to change.
  3. Click Edit instance.
  4. On the Messaging tab, in the Security settings section, perform any of the following actions:
    • To require that the BlackBerry Enterprise Server encrypts messages using S/MIME encryption for a second time when the BlackBerry Enterprise Server processes S/MIME-protected messages that an S/MIME-enabled application weakly encrypted or only signed, in the Turn on S/MIME encryption on signed and weakly encrypted messages drop-down list, click True.
    • To permit BlackBerry device users that have email applications that do not support S/MIME to read the text of an S/MIME-protected message, in the Send S/MIME messages in clear-signed format drop-down list, click True.
    • To require that the BlackBerry Enterprise Server deletes attachment data from any signed-only S/MIME-protected messages so that the BlackBerry Enterprise Server conserves bandwidth, in the Remove attachment data from signed S/MIME messages drop-down list, click True.
    • To require that the BlackBerry Enterprise Server sends encrypted S/MIME-protected messages using an updated MIME content-type that is in accordance with PKCS#7 instead of the default legacy MIME content-type, in the Use PKCS #7 MIME type drop-down list, click True.
  5. Click Save all.
  6. To make sure that the changes take effect immediately, perform the following actions to restart the BlackBerry Messaging Agent:
    1. On the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > BlackBerry Enterprise Server.
    2. Click the BlackBerry Enterprise Server instance that includes the BlackBerry Messaging Agent.
    3. Click Restart instance.