Recommended architecture

Vade Cloud™ performs message analysis outside your network so that it delivers only clean email traffic on your firewall.

Figure 1. Operating architecture of Vade Cloud™

Diagram representing how the Vade Cloud operates and interacts with your network.

MX Setup

In order for Vade Cloud™ to receive emails, the MX fields have to be configured as indicated below:

Table 1. MX List
MX Weight
mx01.cloud.vadesecure.com 10
mx02.cloud.vadesecure.com 10
mx03.cloud.vadesecure.com 10
mx04.cloud.vadesecure.com 10
Tip: Using extra MX records, in addition to the ones listed above (for backup/failover purpose for instance), will result in spam emails bypassing the filtering platform.
Attention: Some DNS hosts require to add a dot at the end of the field in case of absolute notation.

Firewall Rules & Network Access

In order to secure access to the platform, Vade recommends restricting access to port 25 on your firewall to Vade Cloud™ only. As such, you will ensure that no email traffic can bypass the email protection solution.

To do so, authorize the following sub-networks in your firewall configuration for inbound flow:
Table 2. Inbound email flow
Vade Cloud™ IPs Destination servers Ports Comments 
163.172.240.110
163.172.240.111
135.125.122.66
135.125.122.67
 Email server
  • TCP/25 (SMTP)
 French hosters only
LDAP server
  • TCP/389 (LDAP)
  • TCP/636 (LDAPS)
 Authorize if user LDAP verification is activated

If you are using Vade Cloud™ for outbound flow, add the following data in your firewall configuration:

Table 3. Outbound email flow
Sending server Vade Cloud™ hostnames Port Comments
Email server
  • smtp-fr.cloud.vadesecure.com (French hosters only)
or
  • smtp.cloud.vadesecure.com
  • TCP/25 (SMTP)
 To route directly to Vade Cloud™ IPs:
217.74.103.211
195.154.80.82
163.172.55.8
35.181.34.138
35.181.85.71
52.143.135.92