Background
This document will guide you through the configuration of Virtru Gateway rules backed by Office 365 infrastructure. Header check will be added to ensure mail routing loops are prevented.
Specific steps for this section include:
- Create Send Connector
- Create Transport Rule
- Test Rule
Assumptions:
- Mail Encryption Trigger:
-
#secure#
in Subject -
External
Recipient -
Internal
Sender
-
- Mail Flow: O365 > Gateway > Final Delivery
- IP of the gateway is: 1.1.1.1
Skip to:
Diagram of Standard Mailflow
Create Connector
- Login into the Admin Console
- Navigate to the Exchange Admin Portal
- Navigate to the Mail Flow Section
- Navigate to the Connectors Tab
- Create a new Connector
- From: Office 365
- To: Partner Organization
- Name the Connector
- Ex: Virtru Outbound Encrypt
- Enter a description
- Optional
- When to use this connector
- Only when I have a transport rule setup that redirects message to the connector
- How do you want to route email messages
- Route email through these smart hosts
- Ex: 1.1.1.1
- Ex: gw.example.com
- Route email through these smart hosts
- How should Office 365 connect to your partner organization's email server
- Always use TLS
- Any digital certificate
- Validate Connector
- Connector may need to be validated
Note:
If you are using Office 365 for final delivery, please follow the steps in this article to configure the mail relay back to O365.
Transport Rule
- Navigate to the Mail Flow Section
- Navigate to the Rules Tab
Add New Rule
- Enter Rule Details
- Name
- Ex: Virtru Outbound Encrypt
- Conditions
- The Sender is located: Inside the organization
- The Recipient is located: Outside the organization
- Subject Contains: #secure#
- Actions
- Add Header
- Name: X-VIRTRUENCRYPT
- Value: 1
- Use the following connector: Virtru Outbound Encrypt
- Add Header
- Exceptions
- If Header Exists
- Name: X-VIRTRUENCRYPT
- Value: 1
- If Header Exists
- Name
Summary