Online criminals hate us. We protect you from attacks that antivirus can't block.

MailSentry - E-Mail Security and Spamfilter (Setup Guide)

In the following guide, you will learn how to setup up the MailSentry - E-Mail Security and Spamfilter on your DNS. 

MailSentry - E-Mail Security and Spamfilter user interface: https://dashboard.heimdalsecurity.com

MX Records (inbound):
We recommend a preference/cost of 10 for both entries.

  • eu-c01.centiumsecurity.dk
  • eu-c02.centiumsecurity.dk

MailSentry E-Mail Security and Spamfilter IP Addresses:
MailSentry - E-Mail Security and Spamfilter must be able to deliver email to your mail environment. Verify your firewall settings and only allow SMTP from these IP addresses. (Port 25 for SMTP traffic)

  • 89.233.19.180/30
  • 89.233.19.184/29
    Range: (89.233.19.180 - 89.233.19.191)

SmartHost (outbound):

  • eu-outbound.centiumsecurity.dk / port 25, 587 or 2525

SPF (outbound):
Be aware of not removing any 3-party providers delivering e-mails on behalf of your domain.

  • include:_spf.centiumsecurity.dk
    Example: v=spf1 include:_spf.centiumsecurity.dk -all

To review the Inbound / Outbound settings, while logged into the user interface, navigate to the Settings tab, change the domain on the top if you need to review multiple domains, and ensure that the Inbound and Outbound servers are accurate.

Additional Configuration

Switching inbound mail-flow

Once the configuration has completed, the company's MX records can be updated to direct to MailSentry - E-Mail Security and Spamfilter. Please note that updates to MX records may take a few minutes to apply.

MX records for this environment are listed in the Important Information section.

Validation

Message logs can be used to validate mail flow once the MX records are changed to flow email through Centium email security.

Setting up MailSentry - E-Mail Security and Spamfilter with cloud mail providers

Office 365

Inbound configuration in Office 365: Office 365 performs SPF check on all inbound emails and this why the configuration of a transport rule is needed in order to whitelist MailSentry - E-Mail Security and Spamfilter as a mail-relay. MailSentry - E-Mail Security and Spamfilter performs SPF checks on all inbound mails.

The configuration is done in the Exchange Admin Center (EAC) by navigating to Exchange admin > Mail flow > Rules and adding the following IP Addresses to whitelist:

  • 89.233.19.180/30
  • 89.233.19.184/29
    Range: (89.233.19.180 - 89.233.19.191) / (Port 25 for SMTP traffic)

You can read more on using a third-party cloud service with Office 365 on the following link: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/manage-mail-flow-using-third-party-cloud#scenario-1---mx-record-points-to-third-party-spam-filtering

G Suite

Inbound configuration in G Suite: G Suite performs SPF check on all ingoing mails and this is why the configuration of an inbound gateway is needed to whitelist MailSentry - E-Mail Security and Spamfilter as an email-relay. MailSentry - E-Mail Security and Spamfilter performs SPF checks on all inbound mails.

The configuration is done by navigating to Apps -> G Suite -> Settings for Gmail -> Advanced settings -> Spam, Phishing and malware -> Inbound Gateway and adding the following IP Addresses to whitelist: 

  • 89.233.19.180/30
  • 89.233.19.184/29
    Range: (89.233.19.180 - 89.233.19.191) / (Port 25 for SMTP traffic)

It’s recommended to reject all other mails and to require TLS.

You can read more about setting up an inbound email gateway on the following link: https://support.google.com/a/answer/60730?hl=en

The next step is to configure MailSentry - E-Mail Security and Spamfilter. To do that, access the following link: https://support.heimdalsecurity.com/hc/en-us/articles/360007381137-MailSentry-E-Mail-Security-and-Spamfilter-Configuration-

See how to set up and configure MailSentry - E-Mail Security and Spamfilter in the following video:

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.