Defining AS settings for internal partners

How to define settings for AS messages for internal partners.

1. Click the AS Settings tab.
2. Define security for inbound messages.
   1. Navigate to the Inbound Security area.
   2. Set Require signature to indicate whether to require inbound messages to be signed.
   3. Set Require encryption to indicate whether to require inbound messages to be encrypted.
   4. When encryption is required, from the Inbound decryption identification credentials list, select the credentials to decrypt the message.
3. Define security for outbound messages.
   Although these settings control the signing of outbound messages, the Send Messages Unsigned property for a destination can override these settings.
   1. Navigate to the Outbound Security area.
   2. Set Sign outbound messages to indicate whether to sign outbound messages. This setting has no effect on whether to sign an MDN. Signing an MDN is done at the request of a partner and depends on the configuration of an identification credentials set.
   3. From the Signing identification credentials list, select the credentials to sign messages and any outbound MDN that is requested by a partner.
   4. When signature is required, from the Signing digest algorithm list, select the hash algorithm.
   5. When signature is required, from the Signing S/MIME version list, select the S/MIME version to control the format of the micalg parameter value in the Content-Type header of multipart/signed messages.
4. Optional: Define the advanced configuration for AS messages.
   1. Locate the Advanced Settings area.
   2. In the Override AS identifiers field, enter the value to identify partners in the message header.
   3. Set Preserve filename to indicate whether to expose the Content-Disposition header of inbound AS messages in S/MIME format to preserve the original file name that is contained in the header.