Google Message Encryption Administration Guide - Manual (Page 43)

44 Postini Encryption Services Administration Guide
Requirements
Using Message Encryption requires that you route your mail through Outbound
Services. For instructions on how to do this, see the Outbound Services
Configuration Guide.
You will also need to enable Transport Layer Security (TLS) on your mail server.
Setting up TLS on your server ensures that your confidential email is secure
throughout transmission. For information on implementing TLS on your mail
server, check your mail server documentation. If you are using multiple servers,
enable TLS on each server that routes mail to the email protection service.
Billing
Billing for Message Encryption is based on the number of users that have
Message Encryption enabled in the Administration Console.
Message Encryption bills for every user in an organization with org-level Message
Encryption set up, including users that don’t actively use Message Encryption.
Message Encryption also bills for any individual user with user-level Message
Encryption.
For details about pricing and other billing issues, contact your sales
representative.
How Inbox Delivery Works
Inbox Delivery is normally set on the email config level, and directs all outbound
email for all servers in that email config level. You can also set Inbox Delivery for a
specific org or user. You can set Inbox Delivery to send all outbound mail securely,
or only messages that have been marked for encryption. With Inbox Delivery,
outbound mail is first routed to the email protection service, then is encrypted and
sent as an attachment to the recipient. The attachment includes all the tools
needed to set up a password, read the message, and forward or reply to the
message securely.
1. Sender to Email Security Service
Your outbound email is routed through the email protection service. Confidential
messages are sent to the recipient. Other messages are delivered directly to the
recipient’s mail server.
2. Email Security Service to Recipient
Messages routed to Inbox Delivery are encrypted and placed in an HTML file. The
file contains the text of the message (encrypted for security), key information, and
scripts to allow secure decryption. The message is then sent to the recipient.