Using your own SMTP server for sending emails (SaaS)

Majid Latif

Introduction

By default, LogonBox is configured to use a generic SMTP server for any outbound emails that might be sent from your LogonBox.

However, there are many cases where you may want to use your own SMTP server for sending messages. One example could be if you need to set the FROM: address so your users (or email to SMS gateway) will recognise a trusted source address.

Here we will show you how to easily override these default settings.

 

Overriding the default SMTP server settings

To use your own SMTP server  navigate to System Configuration->Configuration and click on the SMS and Email tab. Set the Default Email Provider option to SMTP and select Apply.

 

With the SMTP option enabled navigate to Messages > Settings and select the SMTP tab. button to ON and enter all required details for your outbound email server. In this example we used a gmail SMTP account.

 

Note that From Address and From Name can be set to any value, but this should match whatever address either your users will recognise (or have whitelisted) or to whatever you have configured as a trusted email address (in the case of an SMS to email gateway for example).

Click  to save the changes.

 

Note: The Google Cloud platform, on which LogonBox is hosted, blocks all outbound connections on standard SMTP ports 25, 465 and 587 (unless you are relaying through a G Suite Domain)

Please see this article for more information: https://cloud.google.com/compute/docs/tutorials/sending-mail/

 

Relaying email through your Secure Node

Alternatively, you could opt to relay email via a server inside your company LAN.

As you have already installed a Secure Node so that you can access your User Database (if not, please see here: Installing a Secure Node Agent) you can easily route through the Secure Node for your email also.

First, let's check the Routes for your Secure Node. Navigate to Networking->Routes.

If you chose the default options when configuring your Secure Node, then your Route may already be configured to route everything on your local network.

For example, on this test system, we can route to any host that contains the text hypersocket.io, which is the local LAN, so we will be able to route to a mail.hypersocket.io server without any further configuration (just enter your LAN hostname for your mail server in the STMP settings as detailed above.

 

However if you need to, edit the Route and add in the hostname of the local SMTP server you want to route to by adding the new hostname into the Source tab and clicking the plus icon.

 

Click Update to save the Route change.