If you want to use your MTA to route encrypted and/or signed messages through PGP Universal Server, do the following:
1. Ensure your MTA can route based on content.
2. Configure the following filters.
Rule # Condition Attribute Operator Value 1 Attachment Name is *.pgp 2 Attachment Name is *.gpg 3 Attachment Name is *.asc 4 Message Header content-type Contains multipart/encrypted 5 Message Header content-type Contains multipart/signed 6 Message Header content-type Contains application/pkcs7-mime 7 Message Header content-type Contains application/x-pkcs7-mime 8 Message Header content-type Contains application/pkcs7-signature 9 Any part of message Contains -----BEGIN PGP 10 Any part of message Contains -----BEGIN=20PGP 11 Any part of message Contains * PGP 12 Any part of message Contains LS0tLS1CRUdJTiBQR1Ag 13 Any part of message Contains LS0tQkVHSU4gUEdQI 14 Any part of message Contains LS0tLUJFR0lOIFBHUC
3. If an email matches one of the filters, route it through PGP Universal Server to be decrypted and/or verified.
4. If the email does not match any of the above filters, route the message around PGP Universal Server since it will almost certainly not be encrypted or signed.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Currently server is down.
Didn't find the article you were looking for? Try these resources.