Video Screencast Help

Is the PGP Email Gateway different from PGP Universal Server

Created: 08 Sep 2011 • Updated: 14 Sep 2011 | 1 comment

Hello team,

I am trying to understand the architecture of the PGP Email Gateway, so far, documentations describe PGP email gateway as a seperate appliance. I would like if this can be verified, or know how the PGP Email Gateway architecture works.

 

How does PGP Email Gateway handle external users. PGP web/pdf messenger seems to serve this purpose, however, I would like to know how the PGP pdf/web messenger works in handling external users, or at the very least a dcumentation that can explain this explicitly.

Comments 1 CommentJump to latest comment

jjpenney's picture

PGP Email Gateway and Universal Server are the same thing. The difference is simply how it is used. Email Gateway obviously is intended to process your mail as it passes in to/out of your organisation. Universal Server is intended to manage internal PGP Desktop users (with policies, licences, keys etc...).

PDF and Web Messenger are simply solutions for sending secure mail/attachments to external users who do not have a PGP solution at their end (Note that where possible, traditional PGP key encryption should be used).

PDF Messenger will take the original message and convert it to a PDF document that is only viewable when the correct passphrase is provided (the physical PDF is delivered to the end-user as an attachment and they can open it with Adobe Acrobat as usual, but the passphrase is required to unlock it.)

Web messenger is similar, but the messages are stored on your Universal Server, and the end-user receives an email stating that they must go to your web-page to read their mail. For example, they will go to https://keys.yourdomain.com in their browser, and log in.

With both of the above solutions, the user is initially sent a welcome email, so that they can create their account (and establish a passphrase) on your PGP server.