Manual configuration of connectors and transport rules

If you cannot or do not want to use a wizard to configure Connectors, you can always do this manually.

Warning

CodeTwo strongly recommends using the configuration wizard instead of manually setting up Connectors to avoid mistakes and applying unsupported customization.

To add connectors manually log in to your Office 365 tenant. Go to Admin (Fig. 1.), find Exchange (Fig. 2.) in the left-hand side menu, click on it. In the next screen go to Mail Flow (Fig. 3.).

Access to Office 365 Admin panel.
Fig. 1. Access to Office 365 Admin panel.
Exchange administration shortcut in Office 365 Admin panel.
Fig. 2. Exchange administration shortcut in Office 365 Admin panel.
Mail flow configuration in Exchange On-line dashboard.
Fig. 3. Mail flow configuration in Exchange On-line dashboard.

An inbound and outbound connector must be configured to forward your emails to, and accept processed emails from CodeTwo Email Azure Service.

Proper connectors setup in Office 365.
Fig. 4. Proper connectors setup in Office 365.

Additionally, one transport rule must be added that will be responsible for filtering emails already processed by CodeTwo Email Azure Service to avoid processing loops and signature duplicates.

Proper transport rules setup in Office 365.
Fig. 5. Proper transport rule setup in Office 365.

First, start with creating an inbound connector in the connectors tab. Click the plus icon button to create a new connector. In the pop-up window select From: Your organization's email server, To: Office 365.

Inbound connector configuration.
Fig. 6. Inbound connector configuration.

In the next window provide name for it "CodeTwo Inbound Connector", make sure that checkbox "Turn it on" is enabled, but the checkbox "Retain internal Exchange email headers (recommended)" unchecked.

Inbound connector configuration.
Fig. 7. Inbound connector configuration.

In the last window click on the first radio button and provide the domain name as follows "*.emailsignatures365.com".

Inbound connector configuration.
Fig. 8. Inbound connector configuration.

Next, create an outbound connector. In the pop-up window select From: Office 365, To: Your organization's email server.

Outbound connector configuration.
Fig. 9. Outbound connector configuration.

Provide a name for it "CodeTwo Outbound Connector" and make sure that the "Turn it on" checkbox is enabled, as well as checkbox "Retain internal Exchange email headers (recommended)".

Outbound connector configuration.
Fig. 10. Outbound connector configuration.

In the next step, choose the first option "Only when I have a transport rule set up...".

Outbound connector configuration.
Fig. 11. Outbound connector configuration.

In the following window, add CodeTwo smarthost address. The address must match the geolocation you chose:

  • North Central US (Illinois) - "us-emailsignatures-cloud.codetwo.com"
  • North Europe - "eu-emailsignatures-cloud.codetwo.com".
  • UK South (London) - "uk-emailsignatures-cloud.codetwo.com"
  • Australia East (New South Wales) - "au-emailsignatures-cloud.codetwo.com".
Outbound connector configuration.
Fig. 12. Outbound connector configuration (North Europe).

And finally, in the last step, tick the boxes and radio buttons as visible in the Fig. 13. and make sure that you provided this address "*.codetwo.com" as the domain name on the certificate.

Outbound connector configuration.
Fig. 13. Outbound connector configuration.

Once you're done with connectors, switch tabs to rules. You need to create a new transport rule from a template called "Apply rights protection to messages..." and modify it so it looks exactly like the one presented in Fig. 14.

Proper transport rule configuration.
Fig. 14. Proper transport rule configuration.

Start adding "Apply rights protection to messages..." kind of a rule. Edit the following options as listed below:

  • Name: "CodeTwo Exchange transport rule"
  • Apply this rule if... The sender... is external/internal, Inside the organization
  • Do the following... Redirect the message to... the following connector, CodeTwo Outbound Connector
  • Except if... add exceptions:
    • The sender address... matches "<>",
    • The message type is... "Calendaring",
    • A message header... matches these text patterns, specify header name as "X-CodeTwoProcessed", Enter text pattern, specify words or phrases, add "true"

Leave other options with default settings, except for:

  • Defer the message if rule processing doesn't complete - must be enabled
  • Match sender address in message - change to Header or envelope

Review the results of your changes with Fig. 14. and make sure they look the same.

Was this information useful?