Mimecast provides the ability to test connectivity from your Mimecast account to your internal environment, without contacting Mimecast Support. Testing the connectivity ensures all necessary firewall and application changes have been made prior to swapping services over to Mimecast, or if changing IP addresses internally.
The connectivity tests includes testing:
- Inbound SMTP delivery routes
- POP3 for journaling
- LDAP for Directory synchronization
The tests performed are:
- A ping test to see if contact can be made to the IP address using the PING protocol. This may fail depending on your firewall and security settings.
- Other checks depending on what service is being tested (see the relevant section below).
Inbound SMTP Delivery
- Log on to the Administration Console.
- Select the Administration | Gateway | Policies menu item.
- Select the Delivery Routes menu item from the Definitions drop down
- Click on the Delivery Route to be tested.
- Either click on the:
- Test Connection - Strict TLS button.
- Test Connection - Relaxed TLS button.
- This will run through a series of tests, and generate a summary of the results as shown below:
- Resolves the hostname to IP address.
- Pings the connection.
- Connects to the IP address on SMTP TCP port 25 (or the custom port you have entered).
- Executes SMTP commands to send a test email to the delivery route IP address as follows:
- Checks to see if TLS is supported. If STARTTLS appears in the list of applicable SMTP verbs, an attempt is made to initiate a TLS connection, and send a test email.
- If TLS negotiation fails, the "An Error Occurred" error message is displayed.
- If TLS is successful, the mail send test continues as above.
- Checks to see if there is a certificate, and displays the results:
- If the certificate is not supported, or the certificate is not present, certificate details will not be displayed.
- If the certificate is supported, Mimecast extracts the CN of the certificate, as well as the expiration date. Details for all chained certificates are displayed.
The SMTP connection test will work, even if the delivery route has not been saved. An Administrator can therefore create a new Delivery Route, enter the relevant details, and click test prior to saving the route.
LDAP Directory Connections
To test LDAP connectivity prior to enabling Directory Synchronization:
- Select the Services | Directory Sync menu item.
- Select the Directory Connection, and click the Test Connection button in the top toolbar to start testing
- This will now run through a series of tests, and generates a summary of the results as per below:
- Resolves the hostname to IP address (if the hostname is entered)
- Pings the connection
- Connects to the IP address on LDAP TCP port 389 (or the custom port you have entered)
- Tests the retrieval of one email address in each of the domains you have registered with Mimecast as an Internal Domain. A result of "no results" can be considered a success and indicates that the connection was successful.
- Checks to see if there is a certificate and displays the results
- If the certificate is not supported, or the certificate is not present then certificate details will not be displayed.
- If the certificate is supported, Mimecast extracts the CN of the certificate as well as the expiration date. Details for all chained certificates are displayed.
- Note that if an alternate IP address exists for the Directory Connection, the same tests above are conducted on the backup IP address.
Note: The LDAP Connection test will work even if the Directory Connector has not been saved. An Administrator can, therefore, create a new connector, enter the relevant details, and click test prior to saving it.
POP 3 Journaling
Open the Journal definition, and click the Test Journal Extraction button to ensure that Mimecast will be able to successfully connect to and POP emails from the Journal mailbox.