Zen Software | Blog
Software Distribution for IT Support Companies & MSP's
Skip to content
Become a reseller
Get in touch
SecurityGateway Email Firewall
What types of account-verification can SecurityGateway use?
SecurityGateway can use five different kinds of account verification:
SMTP ‘call-forward’ verification
This method is compatible with all servers, since it uses standard SMTP commands to contact the email server associated with the domain, using the RCPT TO command.
The server needs to allow null senders, or ‘<>’, for this process to work, as required by the RFC. By default, this type of verification uses SMTP port 25.
Exchange / ActiveDirectory
If you are using an Exchange server, or have an ActiveDirectory domain setup, you may use it to verify users exist on the domain.
SecurityGateway does not have support for custom search-filter, like in MDaemon. By default, this type of verification uses port 389.
The Minger option can be used to verify valid users on MDaemon. More information regarding how to setup Minger can be found at the related article below. By default, this type of verification uses port 4069.
If you have a third-party LDAP server setup, you can use LDAP to verify users are valid. Once this option is chosen, you may specify the DN information and the search-filter to search under. By default, this type of verification uses port 389.
If your email server or ActiveDirectory server requires authentication, be sure to specify that information in the appropriate fields to make sure the server does not reject the connection.
Choose this verification type if you wish to utilize Office 365 as a user verification source, and follow the steps below to set it up.
To allow SecurityGateway to access the Office 365 tenant, the Office 365 plan requires Exchange Online. Please make sure the Office 365 plan includes this feature.
To use Office 365 as a user verification source, SecurityGateway requires a service principal that has been granted permission to access the Office 365 tenant. Further, Office 365 utilizes Azure Active Directory as its directory service and a PowerShell module must be installed first. PowerShell 5.1 or higher is required on a 64-bit operating system in order to operate correctly. PowerShell 5.1 is the default build for Windows 10 and Windows Server 2016. Previous operating systems will need to install it from the Windows Management Framework.
Share This Article :