Relevant Product: Exclaimer Cloud - Signatures for Office 365
When using Exclaimer Cloud with a third-party security solution (for example Mimecast; Proofpoint; Barracuda; Reflexion and so on), you may find that emails do not route the way you would like them to or do not have a signature applied.
The following list of smart hosts or security solutions are known to work when using Exclaimer Cloud - Signatures for Office 365:
- Fusemail (Exclaimer Cloud is known to work with Fusemail SecureSMART Suite, but cannot be used with Fusemail Hosted Exchange.)
- Symantec Cloud
If your chosen Smart Host or email security service is not listed above, this does not mean that it cannot be used when using Exclaimer Cloud - Signatures for Office 365.
In the example below, we are using Mimecast, but you can follow the same steps for other Smart Host or third party security systems.
Currently, the connector is set to apply to all messages at the connector level and will likely appear similar to the following connector:
The above setup shows the correct SMTP address for the Mimecast smart host, but this setup bypasses Office 365 Transport Rules.
The objective of this solution is to modify the connector set up so that it uses a Transport Rule with a lower priority than the Exclaimer Transport Rule; therefore, ensuring that signatures are applied before messages are scanned by the third party security solution.
Please follow the steps below to reconfigure your connector:
- Reconfigure the third party security connector
- Add a new mail flow rule
- Configure the new mail flow rule
- Add your .onmicrosoft address to the Exclaimer portal
Reconfigure the third party security connector
- Log on to the Office 365 Portal as a Global Administrator.
- Open the admin center.
- Click admin centers and select Exchange.
- Select mail flow then select connectors.
- Reconfigure the connector to apply Only when I have a transport rule set up that redirects messages to this connector:
- Leave all other connector settings as they are and save the connector.
Add a new mail flow rule
- In the admin center under mail flow, select rules.
- Click the + (plus) button to add a new rule.
- Give the rule a name - for example: Send to Mimecast.
Configure the new mail flow rule
- Scroll down and click the More options link to enable additional rule options.
- Add a condition which states The sender is located inside the organisation. This will ensure that all emails sent from your Office 365 tenancy are routed through the connector.
- Add another condition which states The Recipient is located Outside the organisation. This will ensure that your internal emails sent from your Office 365 tenancy are not routed through the connector, and prevents mail loops.
- Add an action which states Redirect messages to the following connector and select your third party Security connector.
- Click Save to save the new rule. It will now be shown in the rules list with the lowest priority (the greater the number, the lower the priority). Also in this list, you will see an Exclaimer rule called Identify messages to send to Exclaimer Cloud, which has a priority of 1.
Amend the Exclaimer mail flow rule
- Open the rule named Identify messages to send to Exclaimer Cloud.
- Scroll down until you see the option to Stop processing more rules:
- Your Office 365 set up is now complete.
Add your .onmicrosoft address to the Exclaimer portal
The final step of this process is to return to the Exclaimer Cloud portal to ensure emails are routed to Office 365 once the signature has been applied:
Log into the Exclaimer Cloud portal, launch your subscription, then click the options list from the top-right of your screen and select Settings.
The Settings window is displayed, select the Mail Flow tab.
- Under Mail Routing, click Edit.
- From the Mail routing mode drop-down list, select Static domain.
- In Domain name, enter your .onmicrosoft address (listed in your Office 365 tenancy under Domain Name):
- Click Save to save the changes.
Your setup is now complete. When you send a test email, you will be able to see (from the message headers) that the email routes from Office 365 to Exclaimer Cloud, then from Exclaimer Cloud back to Office 365 and from Office 365 to Mimecast - as expected.