Email can be sent and received from any device or application that supports POP and SMTP protocols. This guide outlines how to configure on-premise devices and application servers that need to send (but not receive) outbound mail. For example, application servers that need to send out alerts, and multi-function machines that need to send out scanned documents.
Consider the following:
- If the email client has been configured to use encryption, but the encryption negotiation fails, Mimecast will not accept the connection.
- The Mimecast internal domain user must have the POP and SMTP options enabled before email can be sent and received using these protocols.
- New messages can only be sent outbound via SMTP authentication when using a Mimecast cloud password.
Configuring SMTP Authentication
To configure an SMTP authentication, you must create a specific user account for sending mail (e.g. firstname.lastname@example.org<email@example.com>):
- Log on to the Administration Console.
- Click on the Administration menu item. A menu drop down is displayed.
- Click on the Directories | Internal Directories menu item. A list of your domains is displayed.
- Click on a Domain. A list of the domain's users is displayed.
- Click on the New Address button.
- Fill out the dialog as below:
- Enter the Email Address of the assigned administrator account.
- Enter a Password for the account and make note of it.
- Enable the Password Never Expires setting.
- Enable the Allow SMTP Email Submission setting.
- Click on the Save button.
Configuring the Device for SMTP
Configure the device to:
- Use Mimecast's IP addresses as the SMTP server. See the table below for the IP addresses for your region.
- Use port 587.
- Enable authentication. Use the same login credentials (email address and password) as configured above.
|Mail Server Description|
|The outbound mail server which emails should be sent through. It's important to enable TLS Encryption and to use port 587.||Europe|
Bypassing an Anti-Spoofing Policy
In specific customer accounts, an Anti-Spoofing Policy may be enabled to prevent unauthorized access to your Mimecast mail service. This is evident if during testing, an "550 Anti-Spoofing policy - Inbound not allowed" error is returned. In this instance, enable a bypass policy for your email address(es) in the Administration Console.