[Setup Step 4]: (Optional): Activating Sentinel Messaging for an organization’s outbound email
This article assumes that the organization in question has an active account in Sentinel Messaging, is using our inbound email service, and has its user email addresses registered in our Interface.
Important Note: If you activate Sentinel Messaging Outbound relaying this means that Sentinel Messaging will scan for spam and viruses on outbound emails and block as appropriate.
In order to activate outbound relaying, your reseller / tech contact will need to be notified of the source IP address (es) from where the organization’s connections will be originating from. (This must be the server’s public internet IP address and not it’s private LAN address.
Dynamic IP addresses are not supported at this time. The change takes effect top of the hour and only once you have been notified that outbound has been activated should you proceed to modify the mail server in question to relay all outbound email through Sentinel Messaging. This relay setting is sometimes also known as the “smart host” setting.
The relay/smart host destination where all mail should go is the following 2 options:
- outbound-eu1.ppe-hosted.com. (For EU users)
- outbound-us1.ppe-hosted.com. (For US users)
You can test connectivity to Sentinel Messaging by typing and executing the following from a command prompt on the email server of the organization:
- telnet outbound-eu1.ppe-hosted.com 25
- telnet outbound-us1.ppe-hosted.com 25
You should see a message saying “Welcome to Sentinel Messaging ESMTP Server”, amongst other things. (enter “quit” to close the connection.) If you do not see this message, examine the outbound settings on the firewall between the server and the internet.
Please note: When configuring an Outbound Connector for our smarthosts, authentication is not required. We authenticate the connection by other means (ie, the registered sending server IP on the platform, registered users on the platform, etc).
NB: Please ensure you read the instructions on Firewall Lockdown and include all IP ranges.
- Using Sentinel Messaging for outbound email on top of inbound improves the accuracy of the Sentinel Messaging classification engine in some respects, but especially with bounce emails.
- Remember to remove the outbound configuration from the Sentinel Messaging Interface if no longer being used (otherwise legitimate bounce messages might get quarantined. (which the end-user can just release, if so desired)).
Instructions for outbound setup
You can have your company’s mail server use the Sentinel Messaging SMTP server for outbound mail. This will use the same scanning as the inbound mail. In addition, using the Sentinel Messaging SMTP service will allow you to see the messages in the logs as well.
The pre-requisite for performing an outbound relay is that the domains need to exist in the Sentinel Messaging service prior to Outbound relaying. This is part of the two-tiered authentication we have for SMTP relay. For full step by step instructions click here…
Sentinel Messaging Email Security & Archiving Setup Steps
[Setup Step 1]: Instructions for activating Sentinel Messaging for a domain’s inbound email
[Setup Step 2]: Instructions on importing users
[Setup Step 3]: Firewall Lockdown Options For Email & LDAP Discovery
[Setup Step 4]: (Optional): Activating outbound email protection / DLP
[Setup Step 5]: Data Center – IP Addresses / DNS-MX Records
[Setup Step 6]: Configuring additional features