Domain Diagnosis

Vade Cloud™ provides a domain diagnosis tool which allows you to test the configuration of a domain. To run a diagnosis on a domain.

Tip: Vade recommends running the diagnosis tool every time a new domain is added and before the email traffic is routed to the Vade Cloud™, so that there is always a valid email route for that domain.

Go to Clients > Details > Domains > > Diagnostic to run a diagnosis on a domain.

Inbound Flow

MX declaration verification

This test checks the DNS records for the domain, and tests that the MX entries found point to the Vade Cloud™ platform.

: The MX records were found and point to Vade Cloud™.
: Either no MX records were found for this domain or they do not point to Vade Cloud™.
Important: This must be fixed so that Vade Cloud™ receives your email traffic.
: Either additional MX records were found in addition to both Vade Cloud™ MX records, or just 1 MX record was found pointing to Vade Cloud™ IP address, but not the other.
: The test could not be performed.

Inbound flow

This test checks that downstream servers accept SMTP traffic coming from Vade Cloud™.

: Downstream servers accept traffic coming from Vade Cloud™.
: Downstream servers reject traffic coming from Vade Cloud™.
Important: This must be fixed before routing your traffic to Vade Cloud™ so that the solution delivers your emails to the downstream server.
: At least 1 relay server does not accept traffic from Vade Cloud™ and at least 1 relay server accepts traffic from Vade Cloud™.
: The test could not be performed.

Note: You can edit the user email address used to run this test using the field value and clicking Test again.

Quarantine reports

This test checks that the Vade Cloud™ platform can send quarantine reports from its quarantine servers to the downstream messaging server declared for this domain.

: Downstream servers accept traffic coming from Vade Cloud™.
: Downstream servers reject traffic coming from Vade Cloud™.
Note: The details provided indicate at which SMTP step the transaction failed (HELO, MAIL FROM, RCPT TO, etc.).
: At least 1 relay server does not accept traffic from Vade Cloud™ and at least 1 relay server accepts traffic from Vade Cloud™.
: The test could not be performed.

Access Restriction

This test checks that the downstream server rejects connections from IP addresses other than the Vade Cloud™ ones.

Important: This restriction can only be set if your downstream server is hosted on a dedicated server you manage, and on which you can control the SMTP traffic.

: The downstream server properly rejects connections from foreign IP addresses.
: The downstream server does not accept SMTP traffic from either Vade Cloud™ or any other SMTP server.
: The downstream server does not reject SMTP traffic coming from outside the Vade Cloud™.
Important: This MUST be fixed as the Vade Cloud™ platform should remain the only Mail Exchange Server.
: The access check was not run (in case no downstream server was declared for instance).

User Discovery

This test checks that your environment (LDAP Server, messaging server) supports the User Discovery mode you have set up under User Discovery. Depending on the discovery mode you have chosen, this will check the following:

SMTP

This test checks that your downstream email server rejects unknown recipients (through an SMTP 550 error for the RCPT TO command) and that it replies properly to a known email address (postmaster@<your-domain.com> for instance).

Remember: Some downstream SMTP servers, such as Microsoft Exchange Server 2014 and above, do not support the recipient check.

: The downstream server rejects unknown recipients, which means you may use the RCPT Check discover mode to automatically retrieve a list of users.
: The downstream server does not handle the recipient check. You must use another user discovery method to create the user accounts.

LDAP

This test checks the connection to the LDAP server and that the list of LDAP attributes returned by the directory complies with the User Discovery mode.

You must first set up an LDAP directory under Configure LDAP directories and select LDAP as the User Discovery mode to use.

: The LDAP directory returned the expected attributes to use in the User Discovery mode.
: There was an error connecting to the LDAP server. Refer to the error displayed for more information.
: The LDAP server did not return the expected attributes to try the automatic user discovery. Please refer to the error displayed for further information. There is probably means an error in the Base search, Search Attributes or Search filter fields configured for the LDAP directory.

Outbound Flow

Outbound relays

This test checks that the IP addresses of your messaging server are properly configured as authorized senders for submitting traffic to Vade Cloud™.

Remember: Before using Outbound filtering, you must configure the IP addresses authorized to send outbound traffic to the Cloud platform under Clients > Details > Domains > Details > Outbound > Routing.

Note: You can skip this test's results if you do not want or cannot filter your Outbound traffic through the Vade Cloud™ platform.

: The IP addresses allowed to send outbound traffic to the Vade Cloud™ platform are properly configured.
: The IP addresses allowed to send outbound traffic to the Cloud platform are not properly configured, or not configured at all for outbound filtering.
: At least one messaging server is not allowed to send outbound SMTP traffic from your domain to the Vade Cloud™ platform.

SPF record

If you have set up outbound filtering through the Vade Cloud™ platform, your outbound email traffic will be issued from the Vade Cloud™ platform. If your domain previously had a SPF record listing the IP addresses authorized to emit email traffic from your domain, the led will indicate if you need to change this record or not:

: The SPF record entries match the IP addresses of the Vade Cloud™.
: The SPF record entries point to IP addresses other than Vade Cloud™'s. This needs to be changed so that remote MX can match your SPF record.
: No SPF record was found for this domain.