Usage of a Domain Key with PGP Universal Server 2.x versions
|Article:TECH149885|||||Created: 2010-07-26|||||Updated: 2012-07-03|||||Article URL http://www.symantec.com/docs/TECH149885|
PGP Universal Server supportability to use an external domain key to encrypt all external recipient data.
PGP Universal 2.x
The PGP Universal Server supports encrypting email messages or files to a generic domain key for an external recipient, however the server does not support decrypting email messages or files using a single domain key.
Use the following steps to encrypt all email messages to a domain key of an external recipient:
- Log into the PGP Universal Server admin interface.
- Click Mail > Mail Policy and then select the Outbound Policy Chain.
- Scroll down and click Add Rule.
- Type a name in the Rule Name field.
- In the Conditions section, change the value to If any of the following are true.
- Click the drop down arrow and select Recipient domain
- Leave the second value as is and type the name of the recipient domain.
- Select Actions
- In the Encrypt to section, place a checkmark next to Other Keys/Certificates.
- Click Import. The Import Key or Certificate screen is displayed.
- Import a public key file or key block for the recipient domain and then click Import.
- Optional: Click Key Search and place a checkmark next to Search for keys... and specify a keyserver to search for keys.
- Click Save.
The PGP Universal Server does not support decrypting incoming encrypted mails to a single domain key for the PGP Universal Server's domain. The PGP Universal Server does not include a single key for the entire domain for encryption and decryption.
- The PGP Universal Server 2.x supports mixed key mode environments e.g. SKM, GKM, CKM. This means that users with available existing keys can use their own key and switch between using PGP Desktop for encryption or use the PGP Universal Server Gateway Email feature.
- For version 3.2 and higher which support a PGP group key follow this article, http://www.symantec.com/docs/HOWTO77258
Article URL http://www.symantec.com/docs/TECH149885