SecurityGateway's Secure Messaging feature provides a way for your users to send secure message to recipients outside their domain but in such a way that the message never leaves the SecurityGateway server. It does this by utilizing a secure messaging web portal. When the message is sent, the recipient receives an email notification that a secure message for them is available, with a link to create a Secure Message Recipient account so that they can view the message located on your SecurityGateway server. The secure message is accessed via the recipient's browser, and end-to-end encryption is maintained between the SecurityGateway server and the recipient via HTTPS encryption. Secure messaging requires a valid SSL certificate and that HTTPS is enabled (see also: HTTPS Server). Recipients can view and reply to the messages within the SecurityGateway portal, and they can optionally compose new secure messages to a designated list of users. See: Recipients and Recipient Options for more information on secure message recipient accounts.
|
When using Location Screening to block connections from a particular country, it will not be possible to use Secure Messaging for recipients in that country, because they will not be able to connect to SecurityGateway to view the secure message. |
Sending a Secure Message
To cause a message to be sent using the Secure Messaging system instead of using traditional mail delivery, create a Content Filter or Data Leak Prevention rule that uses the "Send as secure web message" action. For example, you could create a rule that will send a message as a secure message whenever its Subject starts with "[Secure Message]". Alternatively, you can manually create a Sieve Script to send secure messages, using the Sieve action: vnd.mdaemon.securewebmsg.
Enable secure messaging
Check this box to enable the Secure Messaging system.
Automatically create secure messaging recipients
By default whenever a secure message is sent to someone, a Secure Message Recipient account is created for them and a link is provided for them to access the account and view the message. Disable this option if you wish to create all recipient accounts manually.
|
If this option is disabled, secure message recipients must first be manually created on the Recipients page in order for them to receive secure messages. If a rule or script indicates that a secure message should be sent but its recipient is unknown, the message will be bounced back to the sender. |
Exceptions - Domains
If you select a specific domain in the "For Domain:" drop-down list box at the top of the page when configuring these settings, that domain will be listed here after saving the settings. Click the View/Edit link for the corresponding domain to review or edit its Secure Messaging settings, or click Reset to reset the domain's settings to the default Global values.
