Setting Up Your Inbound Email

How to email setup works

External messages destined for your organization must be directed to LibraCyber ESG (On-Premise or Cloud), not left directed to your email server or hosted email service. Once the messages reach LibraCyber ESG, they are processed by our 14 levels anti-spam engine. Only once we are satisfied it is safe to do so, is the message delivered to your organization’s infrastructure or hosted service.

To direct your email traffic to LibraCyber ESG you need to update your domain’s “MX records”. The MX records are stored at your domain host and will direct your email to your mail servers. It’s like registering your new address with the post office so that your mail gets delivered.

LibraCyber ESG supports hybrid environments. As such it can deliver email for one or multiple domains to the following Exchanges:

• Office 365
• On-Premises Mail Servers
• Hosted Exchange (HEX)

In short, to set up your inbound email you need to:

• Add a Domain Relay entry in LibraCyber ESG to specify where the clean emails must be delivered to.
• Modify your MX records to direct inbound emails to your LibraCyber ESG installation.

Add a Domain Relay

Login as administrator to your LibraCyber ESG portal and select Admin Area-> Mail Transport -> Relay Configuration and click New:

• Domain: this is the new domain name you want to add. You can specify also a single email to achieve a special route or include all subdomains by inserting a trailing dot before the domain name: .yourdomain.com
• Mail Server: indicates the final destination mail server where LibraCyber ESG will forward the scanned email to
• Port: the Mail Server port (default 25)
• Use MX: leave this set to No
• Recipient Verification: Select recipient verification policy. (Disabled/ Valid Recipient List /Dynamic Verification)
• Anti-spoofing: Select anti-spoofing verification policy (Enabled / Disabled)

Recipient Verification allows relaying emails only for existent email addresses, and it is a best practice to enable it.

Anti-spoofing is a feature that prevents the relay of email coming from the domain itself unless the sending server is not present in the following Trusted Networks list. For this reason cross-check you added all trusted mail servers that are sending email from your domain through LibraCyber ESG before enabling this feature.

×WARNING: If your mail server is configured to restrict the IP addresses that can deliver inbound emails, ensure these are amended to include LibraCyber ESG IP Addresses.Your firewall must be configured to allow inbound SMTP traffic from LibraCyber ESG.

Office 365

See our How to Configure ESG for Office365 guide for full details.

Modifying Your Domain’s Zone File (MX setup)

Every domain registrar has slightly different MX configuration procedures, but users can use these general steps as guidance.

1. Sign in to your domain’s account at your domain host.
2. Locate the page for updating your domain’s MX records. The page may be named something like “DNS Management”, “Name Server Management”, or “Advanced Settings”.
3. Add new MX records for the ESG mail servers. The destination value is the public name of your ESG appliance. If you have a cluster setup, you need to add two records and choose a relative priority for the nodes: if you give the same priority to a node both will be used for incoming mail, otherwise, the node with higher priority (i.e. a bigger number) will be used, while the other node will be a fallback mailserver.
4. Example values for ESG MX recordsName/Host/AliasTime to Live (TTL)Record TypePriorityValue/Answer/Destination
5. @ or leave blank 3600 MX 10 esva1.example.com
6. @ or leave blank 3600 MX 10 esva2.example.com
7. Delete any existing MX records
8. All other MX records should be deleted, as they are no longer used directly. If you can’t delete the existing MX records, just make sure that they have lower priority than your new ESG records.
9. Save your changes.

×NOTE: MX records changes require some time to take effect. Typically, after 1 to 6 hours you’ll start receiving your mail through ESG, but sometimes it may take up to 48-72 hours. Unfortunately, there is nothing that can be done to speed up this process, but there is also no drawback since in the meanwhile you’ll keep receiving to your mail server directly.