Inbound flow

The purpose of this procedure is to prepare the inbound connector to be implemented prior to the switchover from Vade Cloud to Hornetsecurity.

This configuration is carried out in the administration section of your Microsoft 365 console: https://admin.exchange.microsoft.com/

Incoming mail connector

4. Click on Add a connector
   
5. Click on Partner Organization
6. Then Next
   
7. Add the name of the connector: "Inbound Connector".
8. Then click on Next
   
9. Click on "Checking that the IP address of the sending server matches...".
10. Add the Hornetsecurity server IPs one by one in the field just below. Each addition is validated by clicking on the + icon:
    
11. The Hornetsecurity server IPs to be added are as follows:

12. Then click on Next
13. Check that the "Reject mail if not sent using TLS" box is ticked.
    
14. Then click on Next
15. Check that all information is correct
16. Then click on Create a connector
    
17. The Microsoft 365 interface validates connector registration
18. Then click on OK
    
19. Check that the connector is active: the checkbox must be ticked; if not, it must be deselected.
    

Thank you, you have now completed the configuration of the incoming connector for migration to Hornetsecurity.

Outgoing flow (only for MailOut customers)

The purpose of this procedure is to prepare the connector and the usage rule prior to migration.

This configuration is carried out in the administration section of your Microsoft 365 console: https://admin.exchange.microsoft.com/

Creating the outbound connector

4. Click on Add a connector
   
   
5. Click on Office 365
6. Click on Partner Organization
   
7. Then click on Next
8. Add the connector name "Relay"
   
9. Then click on Next to arrive at Connector usage
10. Check "Only when a transport rule is configured to redirect messages to this connector"
    
11. Then click on Next to access the Routing section.
12. Enter the name of the Hornetsecurity relays host at the beginning of the procedure in the box below, then click on the ➕ to validate the addition. You should add the followings relays one by one:
    • vade-relay-fr01.hornetsecurity.com
    • vade-relay-fr02.hornetsecurity.com
    • vade-relay-eu-fallback01.hornetsecurity.com
    • vade-relay-eu-fallback02.hornetsecurity.com
      
13. Validate this page by clicking on Next to get to the Security restrictions section
    
14. Then click on Next to go to the Validation mail section
15. Enter an address like test@gmail.com outside your domain in the box below then click on the ➕ to validate the addition
    
16. Click on "Validate"
    
17. Wait for validation to complete
18. The message "Validation successful" means that the test e-mail has been accepted by the test address you filled in earlier. If validation fails, continue to the end of the procedure.
    
19. Check that all information is correct
20. Then click on Create connector
    
21. The Microsoft 365 interface validates the connector registration.
    
22. Then click on OK
23. Check that the connector created is active

Create the connector usage rule

4. Click on Add a rule
5. Then on "Create a rule”
   
6. Add a name to the Relay rule, for example
7. Then click on the drop-down list under "Apply this rule if".
8. Select the sender
9. Then in the drop-down list to the right, select is external/internal
   
10. In the window that opens, select Inside the organization
    
11. Then Save
12. Click on the drop-down list under Perform the following operations
13. Select Redirect message to
    
14. In the drop-down list on the right, select the following connector
    
15. In the window that opens, select the connector you've just created
    
16. Then Save
17. Click on Next on the next 2 screens
    
18. Click on Finish on the next 2 screens

Thank you, you have now completed the creation of the outbound connector and the associated rule for migration to Hornetsecurity.

The purpose of this procedure is to add the IP ranges (CIDR) of the Hornetsecurity solution to the inbound gateway already activated for the Vade Cloud solution.

You will have to add those IP ranges to your existing inbound gateway you used for Vade Cloud:

Adding Hornetsecurity IP ranges to the inbound gateway on your Google Workspace administration console

Go to your Google account administration page. Once logged in, go to the Gmail section (Applications > Google Workspace > Gmail).

Then scroll down to the "Spam, phishing and malware" section and click on it. Or to access it directly, click on this link: Spam management

Click on “Add” and add the IP range listed at the beginning of the procedure.

Finish the configuration by clicking on the "Save" button.

Inbound:

Please do not make any changes to your inbound settings

Outbound:

Please proceed as described in "If you are a 'MailOut' customer" and if you are on a private exchange plan additionally do as described here: 

1. Create the connector
   • Be careful to adapt the values entered in the form to your Mailout relay. 
     
     POST /email/exchange/{organizationName}/service/{exchangeService}/sendConnector
     
     
      
2. Obtain connector IDs
   • GET /email/exchange/{organizationName}/service/{exchangeService}/sendConnector
     
     
      
3. Identify the correct connector ID
   • If you have several Ids in the previous result, you now need to test each number to find out which one corresponds to the connector. You'll be able to identify the correct connector when the displayNameis the one you entered previously (see 2-a) Create the connector) displayName "z0Xz0Y" 
     
     GET /email/exchange/{organizationName}/service/{exchangeService}/sendConnector
     
     
      
4. Default connector
   • If you want this connector to be used on all newly created mailboxes, you can configure it as the default send connector.
     In the domainName section, enter the domain name you wish to relay via this connector.
     Please note that the connector will not be applied to existing mailboxes.
     
     PUT /email/exchange/{organizationName}/service/{exchangeService}/domain/{domainName}/changeDefaultSBR
     
     

It's very important to keep the connector identifier "sendConnectorIdDefault" for commissioning on the day of migration.