Connect Process - Request For Information (RFI)

Customers currently using the Connect Application are advised to complete their onboarding setup as soon as possible, as the Connect Application is scheduled to be discontinued on the 31st of January, 2024.

This article contains information on completing the Mimecast Request For Information (RFI) form, detailing required data such as contact details, IP addresses, domains, and forwarding addresses necessary for account setup.

When the contract formalities are completed, you are sent a unique link to an online Request For Information (RFI) form. You must complete this form, as it provides important information about your environment, which is  required by Mimecast before creating your Mimecast account. This information includes the type of Mimecast account, Contact Details, IP Addresses and Domains, and Forwarding Addresses.

Once the RFI has been completed and submitted, the Connect Team will create your Mimecast account. Your Technical Point of Contact is prompted periodically to complete the form, if they have not completed it.

Contact Details

You must specify the contact details of a Technical Point of Contact, and an emergency contact. These details will be used to alert the contacts when a Mimecast event occurs, which requires their attention. Additionally, the email address of the Technical Point of Contact is also used to create the first Mimecast Administrator account.

It is important Mimecast Support is informed immediately when the details for one of these contacts changes.

IP Addresses and Domains

Mimecast uses the IP address and domain information for your environment to deliver inbound emails or accept outbound emails. The form contains the following fields:

Field / Option	Description
Outbound IP Addresses	List the IP addresses that Mimecast will accept outbound emails from (i.e. the internet facing IP addresses of your email server). Hosted Exchange (HEX) providers will be able to supply a list of the required IP addresses.
Inbound IP Addresses	List the IP addresses that Mimecast will deliver inbound emails to (i.e. the internet facing IP addresses of your email server). Hosted Exchange (HEX) providers will be able to supply a list of the required IP addresses.
Inbound Smart Host	List your inbound smart host details, if it is using a dynamic IP address. Most hosting providers (e.g. Microsoft 365, Google Apps) provide an inbound smart host instead of an inbound IP address.
Email Domain Names	List all the domain names that you control, which Mimecast will process emails for (e.g. <domain>.com, <domain>.co.uk, <domain>.co.za, <domain>.za.net).
Third Party Senders	List all other IP addresses that deliver emails using your domain name (e.g. third-party bulk email service). The specified IP addresses are added to the default anti-spoofing bypass policy.

Forwarding Addresses

By default, Mimecast only allows outbound email from the internal domains you have provided. This allows us to ensure only messages originating from your authorized IP addresses are sent. If you forward messages received from your authorized IP addresses to another external domain, they may be blocked by Mimecast in order to avoid unwanted relay services. To avoid this, it is important you list all external addresses that the email server forwards messages.

For example, email for [e-mail] is being forwarded to [e-mail]. In this scenario, Mimecast must know that the [e-mail] can be used as a forwarding address.