What types of account verification can SecurityGateway use?
What types of account-verification can SecurityGateway use?
SecurityGateway can use four 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.
Note that your 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.
Note, however, that SecurityGateway does not have support for custom search-filter, like in MDaemon. By default, this type of verification uses port 389.
If you are using MDaemon 9.63 or later, you can use the Minger protocol to verify users are valid. 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.
KBA-01834 Minger server in MDaemon Pro
KBA-01869 How do I change the user-verification source SecurityGateway uses for a domain?
KBA-01867 How to add a new user-verification source to SecurityGateway